Tags: luau-lang/lute
Tags
Use <= instead of < (visitInterpolatedString) (#345) While working with the `visitor`, I noticed that interpolated strings were not properly traversed. It appears that is bc of this condition, which will not visit the last expression in the interpolated string node's expressions table.
Add lineOffsets field to Luau parser output (#342) This PR enhances the Luau parser to expose line offset information, enabling tooling to better access precise source location mapping for nodes. **Changes Made**: Exposes the computed 'lineOffsets' field to the Luau 'ParseResult'. Modified exisitng ast test serializer tests to work with new apis. Added new test to ensure that line offsets are exposed correctly. ```luau local result = luau.parse("local x = 1\nlocal y = 2") -- result.lineOffsets = { 0, 12 } -- Line 0 starts at char 0, line 1 starts at char 12 ```
Remove luthier.py since it's been superseded entirely by the Luau imp… …lementation. (#337) We no longer need to maintain `luthier.py`, and it poses a frustrating maintenance risk right now to attempt to apply both together. It may be useful in the future to introduce an optional path in the CI to fetch everything from a tarball somewhere and then use cmake/ninja directly instead of running luthier, but we can deal with that when needed.
Pull out new Lute.CLI.lib target to simplify testing (#333) Resolves #315. This PR doesn't currently expose anything more than the old `main` function. As we begin writing tests, we can expand the API of `Lute.CLI.lib`. At a high-level, we make `Lute.CLI` a single-source target whose `main` function simply calls into the `climain.cpp`'s `cliMain` function. This function is identical to our old `main` function but can now be called by unit tests.
PreviousNext