On Mon, Jul 29, 2019 at 9:31 PM George Neuner wrote:
> To me, TypedRacket feels much more like ML than like Dylan or Common
> Lisp. Type inference is great - when it works. Coarse grained scope
> encompassing declarations are great - when you can figure out what
> they should be. Reducing
On Tue, 23 Jul 2019 15:18:26 -0700 (PDT), Atlas Atlas
wrote:
>My personal big wish is "standard library" consistency and futures(like
>more extended date-time functions).
>
>Another big wish is typed system. Typed racket looks like a BIG step
>forward, and gives real benefits, it is shame it
On Tue, 23 Jul 2019 09:22:11 -0700 (PDT), Thomas Dickerson
wrote:
>Since people are talking about running on different "VM" architectures, an
>LLVM backend would be lovely and gives WebAssembly for free.
+1
>JVM support, on the other hand, seems like a particularly poor time
>investment,
I think I found a case where id-a binds id-b when (would-bind? id-a id-b)
returns #f:
(define-syntax bind-test0
(lambda (stx)
(define id #'x)
(define shifted-id (syntax-shift-phase-level id -1))
(displayln (would-bind? id shifted-id))
(syntax-case stx ()
[(_ e)
The macro stepper *should* pop up a dialog after a certain (large)
number of steps and ask if you want to interrupt it and see the
expansion up to that point. For example, try this:
#lang racket
(define-syntax-rule (m) (m))
(m)
The dialog should show up in a second or two. It can't
Hi folks,
I've been lurking in these here forums for a little while now. Over the
years I've looked for the perfect language to implement toy projects in and
nothing seemed quite right. It wasn't until I found Racket a few months ago
that I felt I'd finally come home. Racket seems like an
Unfortunately no. The macro stepper requires macros to fully expand
before it can let you step through them.
You can, however, use this `obs.rkt` file (attached) to debug macros
as they are expanding, and will print the current expanding syntax to
stdout. While not the most convenient thing in
Can I use the macro stepper to debug a bug in some code that seems to be macro
expanding infinitely?
Is it in a sandbox to prevent infinite macro expansion or something?
It looks like DrRacket's background expander allows me to kill expansion after a
short time, but when launching the macro
There is another interesting video
https://www.youtube.com/watch?v=R3zEOsh8AnQ
I think that right approach for racket2 design is think in terms of
neuroscience and cognitive science.
The things whats really mater is *consistency*, in style, in naming, in
logic.
Another important thing is right
On Sun, Jul 28, 2019 at 05:03:16PM -0700, Atlas Atlas wrote:
> пятница, 26 июля 2019 г., 23:35:45 UTC+3 пользователь Hendrik Boom написал:
>
> >
> > One of the great things about Idris is its dependent types, and the
> > way they can be used for (constructive) formal logic. I was
> >
On Fri, Jul 26, 2019 at 04:21:33PM -0400, Hendrik Boom wrote:
> On Fri, Jul 26, 2019 at 01:28:24AM -0700, Mike G. wrote:
> > ??? Make a clear distinction between mutable and immutable data
> >
> > Perhaps make everything immutable except for the contents of boxes
> > (reminiscent of ML). It
Alex, many thanks for the suggestions.
I feel I’m putting too many obstacles in the way. (On the other hand, perhaps
my situation is not so unusual.) I’m trying to make something work with as few
barriers as possible, both for experienced (but non-Racket!) developers, and
for Mac users who
12 matches
Mail list logo
