OH, also, I should mention that it only breaks when using errortrace.
Running it without errortrace seems to work.

~Leif Andersen


On Thu, Feb 1, 2018 at 5:49 PM, Leif Andersen <[email protected]> wrote:
> FWIW, I've managed to shrink the example down even more. Now you only
> need module*, and expose, and two begin-for-syntax blocks after that.
>
> ~Leif Andersen
>
>
> On Thu, Feb 1, 2018 at 5:33 PM, 'William J. Bowman' via Racket
> Developers <[email protected]> wrote:
>> I've encountered a weird bug in DrRacket (I think).
>> I've reproduced the bug in 6.10.1.2 and git HEAD 
>> (02f61622838ff28d447a76c344fe9e117ab5a306).
>>
>> Attached are two files that differ only in the order of two definitions.
>> One produces a namespace mismatch error in DrRacket, the other does not.
>> Neither produces an error when running the files in any other way, such as 
>> in the emacs mode or on the
>> commandline.
>>
>> The key ingredients appear to be:
>> 1. Use require/expose from rackunit-lib
>> 2. Define a macro that uses a phase-1 identifier
>> 3. Define the phase-1 identifiers *after* defining the macro
>>
>> --
>> William J. Bowman
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Racket Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/racket-dev/20180201223310.GO14189%40williamjbowman.com.
>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-dev/CAAVaeEB29JBjq9k_ynJB3hKDcheW6kRtsXqKqXvWxoBBbEFnNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to