Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anchor sound #1500

Open
wants to merge 146 commits into
base: anchor
Choose a base branch
from
Open

Conversation

soumyamahalakshmi
Copy link

Complete Pull

Seth Poulsen and others added 30 commits March 19, 2018 16:59
Handle absolute as well as relative paths (issue brownplt#969)
This isn't user-facing, but avoids us getting npm CRITICAL SECURITY errors
because a tester has an old dependency.

It also has the happy consequence of simplifying some of the parse-test
configuration.
[Reported via email]

In the implementation of the algorithm for reassigning TRO parameters, j-vars
were mixed with j-assigns, which is a type error.

There was no test for this case, which has been added. The algorithm is fine as
far as I can tell and test, it just needed to return JStmts, not JExprs, and do
the wrapping internally for the j-assigns rather than leaving that work until
later.
```
import lists as L

#|  |#

#
```

This code was using the wrong signature for `makeWSToken`, so it wasn't passing in the correct srcloc positions.  (Thanks to Yanyan for finding this bug.)
Fixing a very strange bug in the tokenizer for certain programs
…ms, which causes exceptions rather than reporting the compile errors

[fixes brownplt#1332, fixes brownplt#1013, fixes brownplt#815]

Co-authored-by: Ben Lerner <blerner@users.noreply.github.com>
Fixes brownplt#1480.

Currently, octal escape sequences are parsed incorrectly because the
sequence is evaluated only partially. The "\" delimiter in an octal
sequence like "\101" is already siphoned off during escape sequence
matching, so it is enough to simply parse the match of the numeric
sequence "101".
fix: properly parse octal escape sequences
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants