Oops, sorry about interpreting your question wrong. Unfortunately I don't
know the answer to your actual question.
On Sat, Jan 2, 2021, 10:24 PM Sage Gerard wrote:
> I know about that. I asked why it was designed that way.
>
>
> Sent from ProtonMail mobile
>
>
>
> Original Message -
I know about that. I asked why it was designed that way.
Sent from ProtonMail mobile
Original Message
On Jan 3, 2021, 12:18 AM, Michael MacLeod wrote:
> There's an edge case of 'module' when only one form is provided which results
> in that form being partially expanded to det
There's an edge case of 'module' when only one form is provided which
results in that form being partially expanded to determine if such
expansion would lead to a #%plain-module-begin form. Otherwise (more than
one form provided) they are wrapped in #%module-begin with no partial
expansion occurrin
Why does Racket handle modules with exactly one form differently?
I ran into a bug where modules in my module language won't expand if the
modules have exactly one form, so I'm just curious.
(Wild guess: It's Racket's way of checking for a shortcut to end expansion
earlier)
~slg
--
You receiv
On Sat, Jan 2, 2021 at 4:34 PM Dominik Pantůček <
dominik.pantu...@trustica.cz> wrote:
> Hello Racketeers (and Robby especially)!
>
> On 22. 12. 20 1:30, Robby Findler wrote:
> > Is Typed Racket able to prove that your use of unsafe accessors is
> > actually safe?
>
> Short answer: YES.
>
> One qu
Hello Racketeers (and Robby especially)!
On 22. 12. 20 1:30, Robby Findler wrote:
> Is Typed Racket able to prove that your use of unsafe accessors is
> actually safe?
Short answer: YES.
One question for a start: And what now?
Disclaimer: The following text is by no means intended as critique
to be complete , the form {varriable ← value} with curly brackets used in
simple assignation works too in LET-ARROW*:
scheme@(guile-user)> (let-arrow* ({x ← 1}
{y ← {x + 1}})
x
y)
$2 = 2
but the simpliest form works also:
(let-arrow* (x ← 1
y ← {x + 1
hello,
i made a few macros for scheme syntax improvments.
It uses infix Curly expressions syntax described in SRFI 105
and could be combined to use with SRFI 47 in multi dimensional arrays.
Curly expressions allows out of the box syntax more mathematicals like:
{c > t} instead of (> c t)
my ma
8 matches
Mail list logo