employer
/
tame
1
0
Fork 0
Code Packages Releases Activity
tame/RELEASES.md

415 lines
14 KiB
Markdown
Raw Normal View History

Release notes and associated scripts This begins providing release notes for changes and provides scripts to facilitate this: - tools/mkrelease will update RELEASES.md and run some checks. - build-aux/release-check is intended for use in pipelines (e.g. see .gitlab-ci.yml) to verify that releases were done properly.
2020-04-29 14:40:55 -04:00
TAME Release Notes
==================
This file contains notes for each release of TAME since v17.4.0.
RELEASES.md: Clarification and formatting fix of intro
2020-04-30 13:06:43 -04:00
TAME uses [semantic versioning][]. Any major version number increment
indicates that backwards-incompatible changes have been introduced in that
version. Each such version will be accompanied by notes that provide a
migration path to resolve incompatibilities.
RELEASES.md: Add missing semver link
2020-04-29 15:48:21 -04:00
[semantic versioning]: https://semver.org/
Release notes and associated scripts This begins providing release notes for changes and provides scripts to facilitate this: - tools/mkrelease will update RELEASES.md and run some checks. - build-aux/release-check is intended for use in pipelines (e.g. see .gitlab-ci.yml) to verify that releases were done properly.
2020-04-29 14:40:55 -04:00
TAME developers: Add new changes under a "NEXT" heading as part of the
commits that introduce the changes. To make a new release, run
RELEASES.md: Clarification and formatting fix of intro
2020-04-30 13:06:43 -04:00
`tools/mkrelease`, which will handle updating the heading for you.
Release notes and associated scripts This begins providing release notes for changes and provides scripts to facilitate this: - tools/mkrelease will update RELEASES.md and run some checks. - build-aux/release-check is intended for use in pipelines (e.g. see .gitlab-ci.yml) to verify that releases were done properly.
2020-04-29 14:40:55 -04:00
RELEASES.md: Summary for next release
2021-03-18 09:55:36 -04:00
Remove :map: sym-dep generation This was incorrect to begin with---it does not make sense that an input mapping should depend upon the identifier that it maps to, in the sense that we make use of these dependencies. If we add weak symbol references in the future, then this can be reintroduced. By removing this, we free tameld from having to perform the check itself. .rev-xmlo bumped to force rebuilding of object files since the linker now expects that no such dependencies will exist within them.
2021-07-22 13:39:28 -04:00
NEXT
====
tamer: configure: Check for Rust 1.{52=>53}. Or-pattern syntax is used; I had forgotten to bump this version. For example, match on `Foo(Bar | Baz)` vs. `Foo(Bar) | Foo(Baz)`.
2021-08-30 15:17:06 -04:00
Rust 1.53 is now required.
Remove :map: sym-dep generation This was incorrect to begin with---it does not make sense that an input mapping should depend upon the identifier that it maps to, in the sense that we make use of these dependencies. If we add weak symbol references in the future, then this can be reintroduced. By removing this, we free tameld from having to perform the check itself. .rev-xmlo bumped to force rebuilding of object files since the linker now expects that no such dependencies will exist within them.
2021-07-22 13:39:28 -04:00
Compiler
--------
- Input mappings will no longer emit the destination param as a dependency.
doc: Give @mdash macro an argument This macro is used to consume whitespace so that the following sentence can start on the next line without producing any whitespace in the output. Its argument is, therefore, whitespace. This used to work in earlier versions of Texinfo, but around 6.{6,7} it began failing because an argument was provided when it wasn't defined with one.
2021-08-30 10:30:57 -04:00
Documentation
-------------
- `@mdash` macro now formally defines an argument, correcting errors in
newer versions of Texinfo (~v6.7).
Remove :map: sym-dep generation This was incorrect to begin with---it does not make sense that an input mapping should depend upon the identifier that it maps to, in the sense that we make use of these dependencies. If we add weak symbol references in the future, then this can be reintroduced. By removing this, we free tameld from having to perform the check itself. .rev-xmlo bumped to force rebuilding of object files since the linker now expects that no such dependencies will exist within them.
2021-07-22 13:39:28 -04:00
Linker
------
- Remove exception for input map dependency processing (now that compiler no
longer emits such a dependency).
tamer: tameld: Reduce peak memory usage This clears the buffers used by quick_xml, which was apparently forgotten during initial development (I think I expected it to re-use the previously allocated space automatically). This has significant effects in some cases. For example, one of our UI builds drops from ~9KiB to ~5KiB peak memory usage. Other builds for larger suppliers are only slightly effected because of some of their massive fragments.
2021-08-16 13:38:14 -04:00
- Reduce peak memory usage by clearing buffer of `xmlo` reader between
events.
- How effective this is varies depending on the size of individual
entities within the XML document. In some cases, it can reduce peak
memory usage by half.
Remove :map: sym-dep generation This was incorrect to begin with---it does not make sense that an input mapping should depend upon the identifier that it maps to, in the sense that we make use of these dependencies. If we add weak symbol references in the future, then this can be reintroduced. By removing this, we free tameld from having to perform the check itself. .rev-xmlo bumped to force rebuilding of object files since the linker now expects that no such dependencies will exist within them.
2021-07-22 13:39:28 -04:00
RELEASES.md: Update for v18.0.3
2021-07-21 15:05:52 -04:00
v18.0.3 (2021-07-21)
====================
RELEASES.md: NEXT summary
2021-07-21 15:04:59 -04:00
This release significantly improves the performance of executables
containing large constants, and fixes an optimization-related bug introduced
in v18.0.0.
tame: Ignore duplicate conjunctive predicates in value list optimization error This can occur in generated code (e.g. from proguic if a question-based predicate inherits a predicate already specified). This commit does not change anything that's emitted; it merely allows proceeding. TAMER can be smarter about this; I don't want to invest more time into generalizing deduplication of predicates.
2021-07-19 14:53:25 -04:00
Compiler
--------
tamer: tameld: Place constants into static section in executable This is something that changed when the TAMER POC was initially created, as I was learning Rust. I don't recall the original reason why this was moved, but it could have been moved back long ago. In our systems, constants can hold tables (as matrices) with tens or hundreds of thousands of rows, and there are a number of them in certain projects. As an example, the YAML-based test cases for one of our systems went from ~2m30s to ~45s after this change was made. Much of the cost savings comes from saving GC.
2021-07-21 14:53:15 -04:00
- Place constants into static section in linked executable.
- This was the case in the old linker before the `tameld`
proof-of-concept. The benefits are significant when large constants are
used (e.g. for large tables of data).
tame: Ignore duplicate conjunctive predicates in value list optimization error This can occur in generated code (e.g. from proguic if a question-based predicate inherits a predicate already specified). This commit does not change anything that's emitted; it merely allows proceeding. TAMER can be smarter about this; I don't want to invest more time into generalizing deduplication of predicates.
2021-07-19 14:53:25 -04:00
- Do not report value list optimization error on duplicate conjunctive
predicates.
- This doesn't emit code any differently, it merely permits the situation,
which can occur in generated code.
RELEASES.md: Update for v18.0.2
2021-07-15 23:50:53 -04:00
v18.0.2 (2021-07-15)
====================
RELEASES.md: Summary of NEXT
2021-07-15 23:50:00 -04:00
This is a bugfix release that corrects issues with the Summary Page compiler
and corrects behavior with the new classification system (that is currently
off unless explicitly requested).
summary: Make Summay Page compiler less chatty It produces a lot of output that either results in spam (internal errors) or pollutes the log with unnecessary information.
2021-07-01 13:54:34 -04:00
Compiler
--------
- Make Summary Page less chatty.
worksheet.xsl: Allow package name to auto-generate A long time ago (about a decade), package names were required, but they are now generated by the compiler relative to the root path. The name here was incorrect, which was generating an incorrect path for the linked symbols, which was causing problems with the Summary Page.
2021-07-14 09:51:08 -04:00
- Fix incorrect package name for generated worksheet packages.
compiler: Correct handling of TRUE matches There was a bug whereby TRUE matches would keep whatever value was being matched on, even if it was not a boolean. That was an oversight from the proof-of-concept code, and this fixes it; that's why this is behind a flag! This also adjusts the class aliasing optimization so that it doesn't check for a `TRUE` symbol name, which was a bad idea to begin with. This change also ends up expanding `lv:match[@value="TRUE"]` into the long form, where it didn't previously; this will result in slightly larger xmlo files in some cases, but it's nothing significant, and it does not impact compilation times.
2021-07-15 14:55:32 -04:00
- Restrict `TRUE`-match optimization to classification matches (class
composition).
- This was mistakenly not considering the domain of the match, and
therefore was applying the optimization in situations where it should
not. Results of previous classifications are currently the only place
we guarantee a boolean value.
- Apply classification alias optimization to any `1`-valued constant match.
- Previously applied only to `TRUE`.
summary: Make Summay Page compiler less chatty It produces a lot of output that either results in spam (internal errors) or pollutes the log with unnecessary information.
2021-07-01 13:54:34 -04:00
entry-form.xsl: Correctly generate HTML for params with imported types This is a nearly-10-year-old bug that was introduced when the Summary Page was modified to use the then-new symbol table. The compiler previously concatenated all packages into a single XML tree and processed that, so no package resolution was necessary here before.
2021-07-14 09:59:45 -04:00
Summary Page
------------
- Correctly generate input fields for params using imported types.
- This is a long-standing (nearly 10-year-old) bug.
summary: Make Summay Page compiler less chatty It produces a lot of output that either results in spam (internal errors) or pollutes the log with unnecessary information.
2021-07-01 13:54:34 -04:00
RELEASES.md: Update for v18.0.1
2021-06-24 10:37:25 -04:00
v18.0.1 (2021-06-24)
====================
Remove class-level notice for new system This was not intentionally committed.
2021-06-24 09:59:00 -04:00
This is a minor maintenance release.
Compiler
--------
- Remove internal notice when new system is used to emit code for a
particular classification.
RELEASES.md: Update for v18.0.0
2021-06-23 12:54:25 -04:00
v18.0.0 (2021-06-23)
====================
RELEASES.md: Update with compiler optimizations
2021-06-23 12:46:37 -04:00
This release focuses primarily on compiler optimizations that affect runtime
performance (both CPU and memory). The classification system has undergone
a rewrite, but the new system is gated behind a template-based feature flag
`_use-new-classification-system_` (see Core below). Many optimizations
listed below are _not_ affected by this toggle.
src/current/summary: classify breakdown: Show lv:match/@on values The classification system rewrite removed the debug value collection that previously existed. It didn't make a whole lot of sense anyway, given that that compiler rearranges matches. This falls back to showing the value of the @on, which should be good enough, and is honestly better than what we had before.
2021-06-07 11:41:01 -04:00
Compiler
--------
RELEASES.md: Update with compiler optimizations
2021-06-23 12:46:37 -04:00
- Numerous compiler optimizations including (but not limited to):
- Classification system rewrite with significant correctness and
performance improvements, with significantly less generated code.
- There is more work to be done in TAMER.
- This change is gated behind a feature toggle (see
`_use-new-classification-system_` in Core below).
- Significant reduction in byte count of JavaScript target output.
- Classifications with single-`TRUE` predicate matches are aliases and now
compile more efficiently.
- Classifications that are a disjunction of conjunctions with a common
predicate will have the common predicate hoisted out, resulting in more
efficeint code generation.
- Classifications with equality matches entirely on a single param are
compiled into a `Set` lookup.
- Most self-executing functions in target JavaScript code have been
eliminated, resulting in a performance improvement.
- Floating point truncation now takes place without using `toFixed` in
JavaScript target, eliminating expensive number->string->number
conversions.
- Code paths are entirely skipped if a calculation predicate indicates
that it should not be executed, rather than simply multiplying by 0
after performing potentially expensive calculations.
- A bunch of wasteful casting has been eliminated, supplanted by proper
casting of param inputs.
- Unnecessary debug output removed, significantly improving performance in
certain cases.
- Single-predicate any/all blocks stripped rather than being extracted
into separate classifications.
- Extracted any/all classifications are inlined at the reference site when
the new classification system is enabled, reducing the number of
temporaries created at runtime in JavaScript.
src/current/summary: classify breakdown: Show lv:match/@on values The classification system rewrite removed the debug value collection that previously existed. It didn't make a whole lot of sense anyway, given that that compiler rearranges matches. This falls back to showing the value of the @on, which should be good enough, and is honestly better than what we had before.
2021-06-07 11:41:01 -04:00
- Summary Page now displays values of `lv:match/@on` instead of debug
values.
- This provides more useful information and is not subject to the
confusing reordering behavior of the compiler that is not reflected on
the page.
- Changes that have not yet been merged will remove debug values for the
classification system.
core/aggregate: Remove package This package is not used today. See RELEASES.md for more information; This is a dangerous package that never should have existed. This also fixes the test suite.
2021-06-08 12:00:20 -04:00
Core
----
RELEASES.md: Add _use-new-classification_system_ mention
2021-06-09 16:09:09 -04:00
- New feature flag template `_use-new-classification-system_`.
RELEASES.md: Update with compiler optimizations
2021-06-23 12:46:37 -04:00
- This allows selectively enabling code generation for the new
classification system, which has BC breaks in certain buggy situations.
See `core/test/core/class` package for more information.
core/aggregate: Remove package This package is not used today. See RELEASES.md for more information; This is a dangerous package that never should have existed. This also fixes the test suite.
2021-06-08 12:00:20 -04:00
- Remove `core/aggregate`.
- This package is not currently utilized and is dangerous---it could
easily aggregate unintended values if used carelessly. Those who know
what they are doing can use `sym-set` if such a thing is a good thing
within the given context, and proper precautions are taken (as many
templates already do today).
tamer: Rust 1.{42=>48}.0 for stable intra-doc links without nightly
2021-06-21 13:10:00 -04:00
Rust
----
- Version bump from 1.42.0 to 1.48.0 now that intra-doc links has been
stabalized.
build-aux/progtest-runner: Deterministically concatenate files by name
2021-06-09 16:10:52 -04:00
Miscellaneous
-------------
- `build-aux/progtest-runner` will now deterministically concatenate files
based on name rather than some unspecified order.
src/current/summary: classify breakdown: Show lv:match/@on values The classification system rewrite removed the debug value collection that previously existed. It didn't make a whole lot of sense anyway, given that that compiler rearranges matches. This falls back to showing the value of the @on, which should be good enough, and is honestly better than what we had before.
2021-06-07 11:41:01 -04:00
RELEASES.md: Update for v17.9.0
2021-05-27 13:22:00 -04:00
v17.9.0 (2021-05-27)
====================
RELEASES.md: Entry for TPL
2021-05-10 14:21:24 -04:00
This is a documentation/design release, introducing The TAME Programming
Language in `design/tpl`.
RELEASES.md: Sectioning tweak for recent release
2021-06-08 11:42:09 -04:00
Compiler
-------
- Allow the mapping of flag values from `program.xml`.
RELEASES.md: Entry for TPL
2021-05-10 14:21:24 -04:00
Design
------
- Introduce The TAME Programming Language.
RELEASES.md: Update for v17.8.1
2021-03-18 09:56:02 -04:00
v17.8.1 (2021-03-18)
====================
RELEASES.md: Summary for next release
2021-03-18 09:55:36 -04:00
This release contains a bufix for recent build changes in v17.8.0 that were
causing, under some circumstances, builds to fail during dependency
generation. It also contains minor improvements and cleanup.
RELEASES.md: Mention recent tame and tamed changes
2021-03-15 09:49:57 -04:00
Build System
------------
RELEASES.md: Summary for next release
2021-03-18 09:55:36 -04:00
- [bugfix] Lookup tables will no longer build `rater/core/vector/table` when
build-aux/Makefile.am: Lookup table dependency fix %.xml{=>o}: %csvo rater/core/vector/table.xmlo That is: we'll only build an object file when we try to build another object file. This was causing problems with dependency generation, because it will triggering compilation early.
2021-03-17 17:02:58 -04:00
geneating the `xml` package.
- This was causing problems during `suppliers.mk` dependency generation.
The dependency is still in place for the corresponding `xmlo` file.
- This was broken by v17.8.0.
RELEASES.md: Mention recent tame and tamed changes
2021-03-15 09:49:57 -04:00
- Minor improvements to `tame` and `tamed` scripts to ensure that certain
unlikely failures are not ignored.
RELEASES.md: Summary for next release
2021-03-18 09:55:36 -04:00
RELEASES.md: Update for v17.8.0
2021-02-23 10:51:59 -05:00
v17.8.0 (2021-02-23)
====================
build-aux/Makefile.am (.version.xml): Only change timestamp on hash change The timestamp of the file will now only be updated if the hash (version) _actually_ changes. This allows this to be used as a target dependency without forcing a rebuild each and every time.
2021-02-22 12:37:38 -05:00
This release contains changes to the build system to accommodate
liza-proguic's introduction of step-based packages (in place of a monolithic
`package-dfns.xml`), as well as miscellaneous improvements.
src/current/rater.xsd: Update This had gotten quite out of date from the actual rater.xsd, which existed outside of this repository, that is used during our build process. That was an unintended artifact from moving files around. That file has been removed and symlinked to this one.
2021-02-22 14:39:31 -05:00
Compiler
--------
- `rater.xsd`, used for certain validations of TAME's grammar, has been
updated to an out-of-tree version; it had inadvertently gotten out of
date, and the discrepency won't happen again in the future.
src/current/rater.xsd (yieldsNameType): Remove length checks The intent originally was to try to keep developers to a reasonable name length, but generated identifiers can easily exceed this, and we further do not support namespacing. This can be handled at a template level instead for enforcing naming conventions.
2021-02-22 14:41:23 -05:00
- Further, limits on the length of `@yields` identifiers have been
removed; the lack of namespacing and generation of identifiers from
templates can yield longer identifier names.
src/current/rater.xsd: Update This had gotten quite out of date from the actual rater.xsd, which existed outside of this repository, that is used during our build process. That was an unintended artifact from moving files around. That file has been removed and symlinked to this one.
2021-02-22 14:39:31 -05:00
build-aux/Makefile.am (.version.xml): Only change timestamp on hash change The timestamp of the file will now only be updated if the hash (version) _actually_ changes. This allows this to be used as a target dependency without forcing a rebuild each and every time.
2021-02-22 12:37:38 -05:00
Build System
------------
- Only modify `.version.xml` timestamp when hash changes. This allows
its use as a dependency without forcefully rebuilding each and every time.
build-aux/m4/calcdsl.m4: Do not generate suppliers.mk This will be generated automatically by the Makefile. It's not appropriate to generate in the configure script, and I do not recall why I did so---possibly to work around the issue of delayed tab completion when it needs regeneration? This removes suppmk-gen in favor of more generic Makefile targets---in this case, having `%.tdat` depend upon `rater/core/tdat.xml`, even though that's not quite true (the %.xml file generated from it needs it). But these files are going away soon; a pending TAME optimization branch removes support for the underlying pattern primitive entirely; CSVMs should be used instead.
2021-02-22 12:38:38 -05:00
- `configure` will no longer immediately generate `suppliers.mk`.
- Additionally, `build-aux/suppmk-gen`, which `configure` directly invoked
until now, was removed in favor of generic rules in `Makefile.am`.
src/current/pkg-dep.xsl: Recognize step-level imports First thing to note: this belong in liza-proguic, not here. But it's here right now, so for now I'm making the change. The relationship between TAME and proguic is awkward and will hopefully be improved upon in the near future. As for this actual change: step-level fragments will be concatenated such that the imports will appear at the step level rather than the root.
2021-02-22 12:40:31 -05:00
- Step-level imports in program definitions are now recognized to
accommodate liza-proguic's step-level package generation.
build-aux/Makefile.am: Accommodate step-level packages from proguic Note: this really belongs in liza-proguic, and should be moved in the near future. liza-proguic is being modified to generate step-level packages, which are significantly faster to build than larger ones (XSLT TAME scales terribly). These changes handle those new dependencies. One important thing to note with this change is that suppliers.mk now requires proguic to have run before generation so that those generated dependencies can be properly examined. This is a quick operation, so that is not problematic. This also depends on the .version.xml change that was previously made: when the timestamp changed every time, we got into an infinite build loop.
2021-02-22 12:42:16 -05:00
- Step-level program packages are now properly accounted for as dependencies
for builds.
build-aux/Makefile.am (suppliers.mk): Regenerate when any sources change This should have been done many years ago. This will determine if any of the dependencies have changed for the included suppliers.mk and regenerate it as needed, without the developer having to do so manually when imports change.
2021-02-22 16:47:07 -05:00
- `supplier.mk` is now automatically regenerated when source files
change. This previously needed to be done manually when imports changed.
- `supplier.mk` generation will no longer be verbose (it'll instead be
only one line), which makes it more amenable to more frequent
regeneration.
build-aux/Makefile.am (.version.xml): Only change timestamp on hash change The timestamp of the file will now only be updated if the hash (version) _actually_ changes. This allows this to be used as a target dependency without forcing a rebuild each and every time.
2021-02-22 12:37:38 -05:00
RELEASES.md: Update for v17.7.0
2020-12-09 09:59:09 -05:00
v17.7.0 (2020-12-09)
====================
[DEV-8947] Guided TCO: Reassign argument values after processing all expressions I did say it was _experimental_ guided TRO. This waits to perform the actual argument reassignment until after processing the expressions associated with the new arguments, since they will otherwise be replaced when their original values are still needed.
2020-12-02 14:56:38 -05:00
This release provides tail-call optimizations aimed at the query system in
core.
Compiler
--------
- [bugfix] Recursive calls using TCO will wait to overwrite their function
arguments until all expressions calculating the new argument values have
completed.
[DEV-8947] Make mrange fully tail-recursive and enable TCO We were still having issues with this function when taking the positive branch, when predicates cause many matches within tables. This was causing us to hit stack limits in certain browsers on the Summary Page. This converts it to an iterator so that all branches are tail-recursive, and then enables TCO on them. I was disappointed to find that there's little performance or memory benefit in running our test suite.
2020-12-02 16:50:35 -05:00
`tame-core`
-----------
- `mrange` is now fully tail-recursive and has experimental TCO applied.
- It was previously only recursive for non-matching rows.
RELEASES.md: Update for v17.6.5
2020-12-03 14:09:37 -05:00
v17.6.5 (2020-12-03)
[DEV-8927] Improve summary page performance with new element queries
2020-11-30 15:25:18 -05:00
====================
RELEASES.md (v17.6.5): Add missing subheading I also rephrased it a bit. The original phrasing was not incorrect.
2020-12-09 09:55:34 -05:00
This release improves Summary Page performance when populating the page with
data loaded from an external source.
Summary Page
------------
- Populating the DOM with loaded data now runs in linear time.
[DEV-8927] Improve summary page performance with new element queries
2020-11-30 15:25:18 -05:00
map: Tolerate non-string inputs for `uppercase` and `hash` methods This change simply prevents failure in such situations, (e.g. on invalidated fields in Liza). We'll worry about proper errors and correctness, which ought to be compile-time, in TAMER.
2020-11-23 15:20:20 -05:00
RELEASES.md: Update for v17.6.4
2020-11-23 15:26:54 -05:00
v17.6.4 (2020-11-23)
====================
map: Tolerate non-string inputs for `uppercase` and `hash` methods This change simply prevents failure in such situations, (e.g. on invalidated fields in Liza). We'll worry about proper errors and correctness, which ought to be compile-time, in TAMER.
2020-11-23 15:20:20 -05:00
This release tolerates invalid map inputs in certain circumstances.
Compiler
--------
- Tolerate non-string inputs to `uppercase` and `hash` map methods.
RELEASES.md: Update for v17.6.3
2020-11-03 13:24:36 -05:00
v17.6.3 (2020-11-03)
[DEV-8571] Update the MathJax CDN The MathJax CDN stopped working in April 2017. I updated it to the recommended CDN with the last version from April 2017 to ensure it works like it used to work before the CDN stopped. I added the checksum to ensure the content of the script.
2020-11-03 12:37:38 -05:00
====================
- Update the CDN used to get MathJax.
map: Tolerate non-string inputs for `uppercase` and `hash` methods This change simply prevents failure in such situations, (e.g. on invalidated fields in Liza). We'll worry about proper errors and correctness, which ought to be compile-time, in TAMER.
2020-11-23 15:20:20 -05:00
RELEASES.md: Update for v17.6.2
2020-10-01 10:22:17 -04:00
v17.6.2 (2020-10-01)
====================
[DEV-8362] Include program.mk in project root If a "program.mk" exists in a project's root, it should be included in the Makefile. Co-Authored-By: Anthony Dalfonso <anthony.dalfonso@ryansg.com>
2020-09-30 15:25:43 -04:00
- Optionally include a "program.mk" file if it is present in the project's root
directory. This allows us to move program specific tasks outside of TAME.
Release notes and associated scripts This begins providing release notes for changes and provides scripts to facilitate this: - tools/mkrelease will update RELEASES.md and run some checks. - build-aux/release-check is intended for use in pipelines (e.g. see .gitlab-ci.yml) to verify that releases were done properly.
2020-04-29 14:40:55 -04:00
map: Tolerate non-string inputs for `uppercase` and `hash` methods This change simply prevents failure in such situations, (e.g. on invalidated fields in Liza). We'll worry about proper errors and correctness, which ought to be compile-time, in TAMER.
2020-11-23 15:20:20 -05:00
RELEASES.md: Update for v17.6.1
2020-09-23 16:32:19 -04:00
v17.6.1 (2020-09-23)
====================
[DEV-8492] Fail lv:param-class-to-yields rather than awaiting propagation This problem manifested when the name of the attempted classification is the same name as another object. For example, if we have `t:match-class name="foo"`, and `foo` is a param instead of a class, then `@yields` will fail, and it'd fall back to matching on the param. This is absolutely not what we want. The error message in this context is ugly, but it does work. Example: !!! Unknown match @on (/lv:package/lv:classify/match): `error: unable to determine @yields for class `scheduled_ai' (has the class been imported?)' is unknown for classification --vis-scheduled-ai-type
2020-09-23 15:59:20 -04:00
Compiler
--------
- `lv:param-class-to-yields` will now trigger a failure rather than relying
on propagating bad values, which may not result in failure if the symbol
is represented by another type (non-class) of object.
package{,-lock}.json additions These were being changed every time npm was run.
2020-08-19 15:39:20 -04:00
Miscellaneous
-------------
- `package-lock.json` additions.
RELEASES.md: Update for v17.6.0
2020-08-19 15:30:00 -04:00
v17.6.0 (2020-08-19)
====================
tamed: TAMED_JAVA_OPTS: New environment variable This will be passed to dslc and then to the JVM. The intent is to permit fine-grained heap ratio tuning.
2020-08-14 00:03:01 -04:00
This release provides a new environment variable for JVM tuning. It does
not provide any new compiler features or performance enhancements in itself,
though it enables optimizations through JVM tuning.
Compiler
--------
- The new environment variable `TAMED_JAVA_OPTS` can now be used to provide
arguments to the JVM. This feature was added to support heap ratio
tuning.
RELEASES.md: Include mention of lsimports fix
2020-07-23 14:33:06 -04:00
Miscellaneous
-------------
- `build-aux/lsimports` was causing Gawk to complain about the third
argument to `gensub`; fixed.
bootstrap: Check explicitly for hoxsl symbolic link Using `-e` resulted in a situation where a broken symbolic link would cause `ln` to be executed in error.
2020-07-24 15:33:02 -04:00
- `bootstrap` will test explicitly whether `hoxsl` is a symbol link, since
`-e` fails if the symlink is broken.
RELEASES.md: Include mention of lsimports fix
2020-07-23 14:33:06 -04:00
RELEASES.md: Update for v17.5.0
2020-07-15 11:16:14 -04:00
v17.5.0 (2020-07-15)
====================
[DEV-8130] core: mrange: Use experimental guided TCO This alleviates stack exhaustion issues with large rate tables where the predicates fail to reduce the search space to a reasonable size.
2020-07-14 16:53:05 -04:00
This release adds support for experimental human-guided tail call
optimizations (TCO) to resolve issues of stack exhaustion during runtime for
tables with a large number of rows after having applied the first
predicate. This feature should not be used outside of `tame-core`, and will
be done automatically by TAMER in the future.
`tame-core`
-----------
- `vector/filter/mrange`, used by the table lookup system, has had its
mutually recursive function inlined and now uses TCO.
- This was the source of stack exhaustion on tables whose predicates were
unable to filter rows sufficiently.
Experimental guided TCO This implements TCO in the XSLT compiler by requiring a human to manually indicate when a recursive call is in tail position. This was somewhat urgently needed to resolve stack exhaustion on large rate tables. TAMER will do this properly by determining itself whether a call is in tail position. Until then, this will serve as a test for this type of feature.
2020-07-14 16:50:08 -04:00
Compiler
--------
- Experimental guided tail call optimizations (TCO) added to XSLT-based
compiler, allowing a human to manually indicate recursive calls in tail
position.
- This is undocumented and should only be used by `tame-core`. The
experimental warning will be removed in future releases if the behavior
proves to be sound.
- TAMER will add support for proper tail calls that will be detected
automatically.
RELEASES.md: Update for v17.4.3
2020-07-02 12:48:16 -04:00
v17.4.3 (2020-07-02)
====================
RELEASES.md: Summary for NEXT release
2020-07-02 12:47:12 -04:00
This release fixes a bug caused by previous refactoring that caused
RELEASES.md (17.4.3): Fix {product=>produce} typo
2020-07-15 14:38:07 -04:00
unresolved externs to produce an obscure and useless error for the end
RELEASES.md: Summary for NEXT release
2020-07-02 12:47:12 -04:00
user.
[DEV-8000] ir::asg: Error types for unresolved identifiers during sorting This checks explicitly for unresolved objects while sorting and provides an explicit error for them. For example, this will catch externs that have no concrete resolution. This previously fell all the way through to the unreachable! block. The old POC implementation was catching unresolved objects, albeit with a debug error.
2020-07-01 15:40:21 -04:00
Linker
------
- Provide useful error for unresolved identifiers.
- This was previously falling through to an `unreachable!` block,
producing a very opaque and useless internal error message.
RELEASES.md: Update for v17.4.2
2020-05-13 08:09:48 -04:00
v17.4.2 (2020-05-13)
====================
[DEV-7504] Add GraphML generation We want to be able to build a representation of the dependency graph so we can easily inspect it. We do not want to make GraphML by default. It is better to use a tool. We use "petgraph-graphml".
2020-04-30 14:33:10 -04:00
This release adds GraphML output for linked objects to allow us to
[DEV-7504] Update RELEASES.md to make it less technical
2020-05-13 07:27:34 -04:00
inspect the graph.
[DEV-7504] Add GraphML generation We want to be able to build a representation of the dependency graph so we can easily inspect it. We do not want to make GraphML by default. It is better to use a tool. We use "petgraph-graphml".
2020-04-30 14:33:10 -04:00
Linker
------
- Add `--emit` oprion to `tamer/src/bin/tameld.rs` that allows us to specify
the type of output we want.
[DEV-7504] Update RELEASES.md to make it less technical
2020-05-13 07:27:34 -04:00
- Minor refactoring.
[DEV-7504] Add GraphML generation We want to be able to build a representation of the dependency graph so we can easily inspect it. We do not want to make GraphML by default. It is better to use a tool. We use "petgraph-graphml".
2020-04-30 14:33:10 -04:00
Miscellaneous
-------------
[DEV-7504] Add make target for "graphml"
2020-05-01 13:33:41 -04:00
- Added `make` target to build linked GraphML files.
- Updated `make *.xmle` target to explicitly state it is emitting `xmle`.
[DEV-7504] Add cypher script for post-graph import After we import the GraphML output into Neo4J, we need to make a few modifications to make the data easier to work with.
2020-05-13 07:24:02 -04:00
- Added Cypher script to use in Neo4J after a GraphML file is imported.
RELEASES.md: Fix tame-core heading
2020-04-29 15:49:57 -04:00
- `RELEASES.md`
- Add missing link to semver.org.
- Fix `tame-core` heading, which was erroneously Org-mode-styled.
RELEASES.md: Clarification and formatting fix of intro
2020-04-30 13:06:43 -04:00
- Rephrase and correct formatting of an introduction paragraph.
RELEASES.md: Add missing semver link
2020-04-29 15:48:21 -04:00
RELEASES.md: Update for v17.4.1
2020-04-29 15:34:29 -04:00
v17.4.1 (2020-04-29)
====================
Release notes and associated scripts This begins providing release notes for changes and provides scripts to facilitate this: - tools/mkrelease will update RELEASES.md and run some checks. - build-aux/release-check is intended for use in pipelines (e.g. see .gitlab-ci.yml) to verify that releases were done properly.
2020-04-29 14:40:55 -04:00
This release refactors the linker, adds additional tests, and improves
errors slightly. There are otherwise no functional changes.
Compiler
--------
- Refactor proof-of-concept dependency graph construction code.
- Improvements to error abstraction which will later aid in reporting.
Miscellaneous
-------------
- `RELEASES.md` added.
- `tools/mkrelease` added to help automate updating `RELEASES.md`.
- `build-aux/release-check` added to check releases.
- This is invoked both by `tools/mkrelease` and by CI via
`.gitlab-ci.yml` on tags.
v17.4.0 (2020-04-17)
====================
This release focuses on moving some code out of the existing XSLT-based
compiler so that the functionality does not need to be re-implemented in
TAMER. There are no user-facing changes aside form the introduction of two
new templates, which are not yet expected to be used directly.
RELEASES.md: Fix tame-core heading
2020-04-29 15:49:57 -04:00
`tame-core`
Release notes and associated scripts This begins providing release notes for changes and provides scripts to facilitate this: - tools/mkrelease will update RELEASES.md and run some checks. - build-aux/release-check is intended for use in pipelines (e.g. see .gitlab-ci.yml) to verify that releases were done properly.
2020-04-29 14:40:55 -04:00
-----------
- New `rate-each` template to replace XSLT template in compiler.
- New `yields` template to replace XSLT template in compiler.
- Users should continue to use `rate-each` and `yields` as before rather
than invoking the new templates directly.
- The intent is to remove the `t` namespace prefix in the future so that
templates will be applied automatically.
Compiler
--------
- XSLT-based compiler now emits `t:rate-each` in place of the previous XSLT
template.
- XSLT-based compiler now emits `t:yields` in place of the previous XSLT
template.