Re: [racket-users] Reimplementing Hackett’s type language: expanding to custom core forms in Racket

[Stephen Chang]

Hi Alexis,

Great article. And timely too, since it addresses some of the same
usage issues of local-expand and stoplists that we ran into with
Turnstile.

(I'm also interested in why the core forms are added to the stop list.
Is it because of let-syntax? I know it's probably been mentioned
before but I wasn't able to find an explanation in the docs or
archive.)

Specifically, we (Michael Ballantyne) recently added stoplists for
terms, but we're still experimenting with the right representation for
types.

In our experimentation we manually implemented the recursive,
stop-listed expansions like you did (but it wasny as elegant as your
syntax classes). I eventually ran into the same issue with binding
types and passing the context, so it was good to see a solution worked
all the way through, and written up nicely.

In the future, I would love to receive notification about any new blog posts.

On Sun, Apr 15, 2018 at 10:38 AM, David Thrane Christiansen
 wrote:
> Hi Alexis,
>
> I am very happy to have posts like this announced here. Thanks for writing
> it! It was useful and interesting.
>
> David
>
> On Sun, Apr 15, 2018, 06:58 Alexis King  wrote:
>>
>> Hello all,
>>
>> I wrote a blog post about my recent experience rewriting the
>> implementation of Hackett’s internal type representation, and on writing
>> languages that expand to custom core forms in Racket in general. For
>> those interested in Hackett and/or (ab)uses of some of the lesser-known
>> features of Racket’s macro system, you might be interested:
>>
>>
>> https://lexi-lambda.github.io/blog/2018/04/15/reimplementing-hackett-s-type-language-expanding-to-custom-core-forms-in-racket/
>>
>> I’ve refrained in the past from posting my blog to this list, since it
>> does not seem like something other people normally do and many of the
>> interested parties seem to find it through some other channel. Still, I
>> thought I’d try posting it here this time. Feedback is welcome and
>> appreciated, both on the blog post itself and on whether or not people
>> appreciate posting things like this to this list.
>>
>> Alexis
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Racket Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to racket-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Reimplementing Hackett’s type language: expanding to custom core forms in Racket

[David Thrane Christiansen]

Hi Alexis,

I am very happy to have posts like this announced here. Thanks for writing
it! It was useful and interesting.

David

On Sun, Apr 15, 2018, 06:58 Alexis King  wrote:

> Hello all,
>
> I wrote a blog post about my recent experience rewriting the
> implementation of Hackett’s internal type representation, and on writing
> languages that expand to custom core forms in Racket in general. For
> those interested in Hackett and/or (ab)uses of some of the lesser-known
> features of Racket’s macro system, you might be interested:
>
>
> https://lexi-lambda.github.io/blog/2018/04/15/reimplementing-hackett-s-type-language-expanding-to-custom-core-forms-in-racket/
>
> I’ve refrained in the past from posting my blog to this list, since it
> does not seem like something other people normally do and many of the
> interested parties seem to find it through some other channel. Still, I
> thought I’d try posting it here this time. Feedback is welcome and
> appreciated, both on the blog post itself and on whether or not people
> appreciate posting things like this to this list.
>
> Alexis
>
> --
> You received this message because you are subscribed to the Google Groups
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[racket-users] Reimplementing Hackett’s type language: expanding to custom core forms in Racket

[Alexis King]

Hello all,

I wrote a blog post about my recent experience rewriting the
implementation of Hackett’s internal type representation, and on writing
languages that expand to custom core forms in Racket in general. For
those interested in Hackett and/or (ab)uses of some of the lesser-known
features of Racket’s macro system, you might be interested:

  
https://lexi-lambda.github.io/blog/2018/04/15/reimplementing-hackett-s-type-language-expanding-to-custom-core-forms-in-racket/

I’ve refrained in the past from posting my blog to this list, since it
does not seem like something other people normally do and many of the
interested parties seem to find it through some other channel. Still, I
thought I’d try posting it here this time. Feedback is welcome and
appreciated, both on the blog post itself and on whether or not people
appreciate posting things like this to this list.

Alexis

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.