> On Oct 3, 2017, at 5:21 PM, Alexis King wrote:
>
> I realized I probably also ought to post my workaround, which I use in
> Hackett: I just don’t use preserved syntax properties at all (only
> unpreserved ones). I found that sticking syntax objects in preserved
> syntax properties was unreliab
I realized I probably also ought to post my workaround, which I use in
Hackett: I just don’t use preserved syntax properties at all (only
unpreserved ones). I found that sticking syntax objects in preserved
syntax properties was unreliable, probably for the reasons Matthew
mentioned in the aforemen
I am not sure what could be causing this problem, but it seems related
to something I ran into about a year ago[1], though I was getting
slightly different behavior. At the time, Matthew had the following to
say on the subject:
> On Oct 25, 2016, at 4:28 PM, Matthew Flatt wrote:
>
> Putting iden
Hello,
I'm getting an error that only happens when I split a definition and a use into
two small files, def.rkt and use.rkt. If I put them into the same file, the
error goes away.
The error happens when I call `syntax-local-value` on an identifier stored in a
syntax property, while compiling u
