lalrpop/RELEASES.md

346 lines
12 KiB
Markdown
Raw Normal View History

2019-01-20 17:29:54 +01:00
<a name="0.16.3"></a>
## 0.16.3 (2019-01-20)
#### Performance
* Avoid some memcpying in reductions ([4968e5a6](https://github.com/lalrpop/lalrpop/commit/4968e5a60822a14a190974668bcf194129358acf))
#### Bug Fixes
* Allow the deprecated use of trim_left ([bdd65184](https://github.com/lalrpop/lalrpop/commit/bdd65184e539bdeca47f8bae031160f5e51b3375), closes [#428](https://github.com/lalrpop/lalrpop/issues/428))
* Don't make generated files read-only ([0c67bbed](https://github.com/lalrpop/lalrpop/commit/0c67bbed06cdd86da0264d21a9aa0a86ab88adad))
2018-11-28 19:56:04 +01:00
<a name="0.16.2"></a>
# Version 0.16.2 (2018-11-22)
## Fixes
* Fix type annotation for inline actions
Thanks to the following contributors:
- @tjade273
2018-10-27 13:42:24 +02:00
<a name="0.16.1"></a>
# Version 0.16.1 (2018-10-27)
## Features
* Add a setting to strip indentation from the generated grammar ([9f3a978f](https://github.com/lalrpop/lalrpop/commit/9f3a978fde1a6a86c907cfbd27654032fdcb1d5c))
* Allow setting features from the commandline ([c8df4987](https://github.com/lalrpop/lalrpop/commit/c8df49872d50019feb6b742aa22fde8c7c94552d))
* Don't depend on lalrpop-snap to compile lalrpop ([3ff1b4c4](https://github.com/lalrpop/lalrpop/commit/3ff1b4c45fb853eb2dd337d7189644e515d87521))
* Allow setting out_dir on the command line ([9c26e517](https://github.com/lalrpop/lalrpop/commit/9c26e5177e6c910b8d51062795a245840a946d93))
* Let parse rules be conditionally compiled ([e6b6a07f](https://github.com/lalrpop/lalrpop/commit/e6b6a07fd694fa795c6999fcb879a331d6f04256))
## Fixes
* Process escape sequences in string literals appearing as terminals ([0b7e1e1d](https://github.com/lalrpop/lalrpop/commit/e915302bbf75674ef22423dc5a925e5d0b7e1e1d))
Thanks to the following contributors:
- @Marwes
- @jimblandy
2018-09-03 19:13:37 +05:30
# Version 0.16.0
Features:
- Allow attributes to be specified in larlpop_mod! (#398)
Fixes:
- Don't generate reduce actions which do not fit in
the integer size (#399)
- Generate files in OUT_DIR (#353)
Dependencies:
- Update atty (0.2), bit-set (0.5), ena(0.9) (#374)
- Regex to 1.0 (#375)
Thanks to the following contributors:
- @Marwes
- @KRITZCREEK
- @asyosec
- snsmac
- Eijebong
- @sanxiyn
2018-04-28 12:28:06 +02:00
# Version 0.15.2
Features:
- Make semicolon after `}` in rules optional (#355)
Fixes:
- Use hash to decide whether to recompile (#369)
- Reduce the compile times of generated parse table parsers (#366)
Thanks to the following contributors for this release:
- @matklad
- @psl8
- @Marwes
2018-04-04 23:42:51 +05:30
# Version 0.15.1
Fixes:
- Don't overflow the stack in parse table debug builds (#337)
- Use the correct type for `!` in macro expanded productions (#335)
- Allow lalrpop parsers to be used with include! (#338)
- Remove dependency on docopt, rustc-serialize, update itertools (#344, #345)
- Correctly anchor regex at the beginning (#358)
Thanks to the following contributors for this release:
- @Marwes
- @mbrubek
- @waywardmonkeys
- @sanxiyn
- @17cupsofcoffee
- @matklad
2018-03-18 12:52:33 +01:00
# Version 0.15
Features:
- The source and binary size of generated parsers has been reduced (#324, #306)
- Regex compilation as part of the generated lexer can now be cached (#318)
- The documentation is now provided as a [mbbook](http://lalrpop.github.io/lalrpop/) (#298)
Bugs fixed:
- Fixed a stack overflow in debug builds of large grammars (#337)
- The error terminal now gets the correct type assigned when part of macros (#335)
- Character literals now parse correctly in the parser files (#320)
Compatibility notes:
- To let regex compilation be cached, each parser are now generated as a struct
with a `parse` method instead of just a function.
To upgrade, change each parse call from `parse_X(..)` to `XParser::new().parse(..)`.
2018-03-18 12:52:33 +01:00
Thanks to the following contributors for this release:
2018-03-22 13:38:37 -04:00
- @Phlosioneer
- @waywardmonkeys
- @brendanzab
- @dtkerr
- @Marwes
- @ahmedcharles
- @udoprog
2018-03-18 12:52:33 +01:00
2018-01-24 05:52:31 -05:00
# Version 0.14
Bugs fixed:
- Infinite loop in error recovery fixed (#240).
- Bad error messages if a `;` was forgotten fixed (#276).
- Grammar errors were sometimes incorrectly reported as "extra tokens" (#278)
- `extern` blocks now allowed even when not using a custom tokenizer (#261)
- `ParseError` now implements `Display`
- actions can now return a grammar's type parameter's associated type (#247)
- generated files are now rebuilt when there is a new LALRPOP version (#243)
Compatibility notes:
- As part of making `ParseError` implement `Display`, the default
error type changed from `()` to `&'static str`, so parse errors type
may change from `lalrpop_util::ParseError<..., ()>` to
`lalrpop_util::ParseError<..., &'static str>`.
Thanks to the following contributors for this release:
- @fitzgen
- @joerivanruth
- @pyfisch
- @nick70
- @notriddle
- @vmx
2017-06-16 15:47:18 -04:00
# Version 0.13.1
- We now support `#![..]` attributes in `.lalrpop` files.
- We now use lane table by default: since the lane table algorithm
automatically generates compressed tables where possible, the
`#[lalr]` attribute is still accepted, but has no effect.
- If you encounter problems, please report bugs! In the meantime,
though, you can use the `LALRPOP_LANE_TABLE=disabled` environment
variable to change back.
- When the `<>` string is found within `{}` inside of an action, it
now generates a series of `x: x` pairs for each named value `x`.
This is useful for struct constants, since you can do something
like: `<a:Foo> <b:Bar> => MyStruct { <> }`, if `MyStruct` had two
fields named `a` and `b`.
- We now support character literal patterns in the external tokenizer pattern syntax.
- The lalrpop executable now supports `--version`.
- We are (for now, at least) testing for compatibility with Rust 1.13.
This minimal supported rustc version may change in the future,
however.
- Misc bug fixes.
Thanks to the following contributors for this release:
- @jchlapinski
- @minijackson
- @nikomatsakis
- @ravenexp
- @ruuda
- @wieczyk
- @withoutboats
2017-04-07 05:44:20 -04:00
# Version 0.13
This is a bug release for LALRPOP. First, we have two major improvements to the
generated lexer:
- The lexer now generates code that uses the `regex` crate. This
results in **far** less code than the older style, and seems to
preserve performance.
- The lexer now supports custom priorities for regular expression tokens,
making it possible to support case-insensitive keywords.
- See the [calculator2b example] for details.
Second, we have a **beta release** of the new lane-table based
LR-table generation. Lane tables handle the full set of LR(1)
grammars but typically reduce **much** smaller state tables. This
feature eliminates the need to manually mark grammars as `#[LALR]`.
Lane tables are **not** on by default; you can enable them by setting
`LALRPOP_LANE_TABLE=enabled` in your environment (use
`std::env::set_var` in your `build.rs`).
[calculator2b example]: https://github.com/nikomatsakis/lalrpop/blob/master/doc/tutorial.md#calculator2b
Finally, the `lalrpop` executable now has the ability to generate
standalone reports (`--report`).
Fixed bugs:
- Fix #157: We now recognize single quote (`'`) properly in our tokenizer.
- Fix #179: Fix bug in recursive ascent code generation.
Thanks to the following contributors to this release:
- @ahmedcharles
- @king6cong
- @nikomatsakis
- @nixpulvis
- @wagenet
- @wieczyk
2016-02-28 05:36:50 -05:00
2017-02-11 08:10:37 +01:00
# Version 0.12.5
- Add the expected successor tokens to `UnrecognizedToken` errors ([thanks @Marwes!](https://github.com/nikomatsakis/lalrpop/pull/178)).
- Fix to error recovery doing a bad cast ([thanks @Marwes!](https://github.com/nikomatsakis/lalrpop/pull/182)).
# Version 0.12.4
2016-11-23 05:23:10 -05:00
2016-11-23 04:21:44 -05:00
Major new feature! @Marwes
[added support for error recovery](https://github.com/nikomatsakis/lalrpop/pull/160).
There have also been a number of other improvements:
2016-11-23 05:24:21 -05:00
- The `ParseError` type now implements `Error` and `Display` ([thanks @Marwes!](https://github.com/nikomatsakis/lalrpop/pull/167)).
- We no longer emit comments in generated code by default ([thanks @Marwes!](https://github.com/nikomatsakis/lalrpop/pull/165)).
2016-11-23 04:21:44 -05:00
# Versions 0.12.2, 0.12.3
2016-11-28 12:55:49 -05:00
(Yanked due to minor backwards incompatibility.)
2016-09-29 05:37:48 -04:00
# Version 0.12.1
Bug fix release. Major bugs addressed:
- ["LR1 TLS not installed"](https://github.com/nikomatsakis/lalrpop/issues/145);
- [False conflicts in the LR(1) code generator](https://github.com/nikomatsakis/lalrpop/issues/144).
Also, there is now a tutorial for writing custom lexers.
[Thanks @malleusinferni!](https://github.com/nikomatsakis/lalrpop/pull/131).
# Version 0.12
**Enabled a new table-driven code-generator by default.** This generates
2016-08-02 21:44:15 -04:00
less code than the older recursive-ascent-based generation scheme, but
may parse less efficiently. To go back to the old scheme, annotate
the grammar declaration:
```
#[recursive_ascent] grammar;
```
Also, **the syntax for requesting LALR-generation has changed** to use
2016-08-02 21:44:15 -04:00
an annotation:
```
#[LALR] grammar;
```
We no longer **emit module-level attributes**, which means that unused
imports in your .lalrpop file may start getting warnings. [Thanks
@dflemstr!](https://github.com/nikomatsakis/lalrpop/pull/118)
An overflow bug in LALRPOP was
fixed. [Thanks @larsluthman!](https://github.com/nikomatsakis/lalrpop/pull/120)
We no longer depend on `time`, but now use
`std::time`. [Thanks @serprex!](https://github.com/nikomatsakis/lalrpop/pull/121)
There is now a `Configuration` object for use in your `build.rs`
scripts. And,
[thanks to @dflemstr!](https://github.com/nikomatsakis/lalrpop/pull/108),
it permits you to configure the directory where LALRPOP output is
generated.
Fixed a bug in the LALRPOP option
parsing. [Thanks @Nemikolh!](https://github.com/nikomatsakis/lalrpop/pull/106)
Various typos and small corrections. Thanks [@reuben](https://github.com/nikomatsakis/lalrpop/pull/1103) and [@ashleygwilliams](https://github.com/nikomatsakis/lalrpop/pull/116)!
2016-02-28 05:36:50 -05:00
# Version 0.11
2016-02-19 05:50:21 -05:00
Updated to use the `regex-syntax` crate for regular expression
parsing instead of rolling our own parser. This means we can now
support the [same regular expression syntax as the regex crate](https://doc.rust-lang.org/regex/regex/index.html#syntax),
and in particular can support unicode character classes like `\p{Greek}`.
Note that some regex features -- such as non-greedy repetition and
named capture groups -- are still not supported (or just not meaningful).
2016-02-24 06:07:28 -05:00
Optimized LR(1) construction time by approximately 5x.
2016-02-25 05:59:32 -05:00
Improved handling of location tokens `@L` and `@R` so that they can be
freely used without ever causing parse conflicts.
2016-02-19 05:50:21 -05:00
# Version 0.10
2016-01-23 11:43:50 -05:00
Major update to LALRPOP error messages in cases of shift/reduce and
reduce/reduce conflicts. The messages now try to explain the problem
in terms of your grammar, as well as diagnosing common problem
scenarios and suggesting solutions.
2016-02-19 04:09:29 -05:00
Added a standalone LALRPOP executable.
2016-02-19 04:26:32 -05:00
We no longer generate incomplete files when grammar generation fails
(Issue #57).
# Version 0.9
Miscellaneous bug fixes, mostly. Processing for a `build.rs` file now
starts from the project directory, rather than being hardcoded to
start from `src`.
# Version 0.8
2015-10-15 13:11:12 -04:00
2015-10-25 07:34:08 -04:00
Add support for inlining nonterminals. Nonterminals can now be
annotated with `#[inline]`. If you do so, each use of the nonterminal
will be inlined into its place. This can be very helpful in addressing
shift-reduce or reduce-reduce conflicts, at the cost of a larger
grammar. We now inline `Foo*`, `Foo?`, and `(Foo Bar)` nonterminals by
default.
2015-10-15 12:34:16 -04:00
# Version 0.7
This is mostly a bug-fix release.
Various minor issues were addressed:
- Issue #25: Unbalanced parens in string literals appearing in code now work properly.
- Issue #32: Regular expression parsing consumed infinite memory when a `.` appeared.
- Issue #34: Automatic tokenizer generation did not play well with generic type parameters.
# Older versions
I hadn't yet started writing release notes, sorry.