Re: [racket-dev] define-syntax in typed/racket/base

> On Oct 3, 2015, at 3:59 PM, Antonio Menezes Leitao > wrote: > > Hi, > > It seems that define-syntax is provided by typed/racket but not by > typed/racket/base. Is that on purpose? > > The following program compiles in DrRacket, version > 6.2.900.17--2015-09-20(6dfc20d/a) [3m]: > > #lang

Re: [racket-dev] define-syntax in typed/racket/base

Is the problem still there when you (require (for-syntax racket/base))? > On Oct 3, 2015, at 4:46 PM, Antonio Menezes Leitao > wrote: > > BTW, the same problem occurs with define-sequence-syntax. > > On Sat, Oct 3, 2015 at 8:59 PM, Antonio Menezes Leitao >

Re: [racket-dev] Racket Cheat Sheet

What's wrong with define-simple-macro ? I think it's clearer about what it does than define-syntax-rule. > On Oct 7, 2015, at 2:10 PM, Jay McCarthy wrote: > > I agree. I don't like the name. I think define-syntax-rule is a choice > choice name. > > On Wed, Oct 7, 2015 at 2:01 PM, Jack Firth w

Re: [racket-dev] Release for v6.3 has begun

Would it make sense to revert the commit that changed (set-implements? (mutable-set) 'set-add) and (set-implements? (set) 'set-add!) to both return true? In previous version they returned false, and it does seem like returning false is a good idea. I think it was this commit here: https://githu

Re: [racket-dev] colon keywords

Should we make this into a meta-language? #lang colon-kw racket (define (a:b a :b c) (+ a c)) (a:b -1 :b -5) That way it would not be a change to racket and it wouldn't break everything, but those who want it can have it. > On Oct 14, 2015, at 7:51 AM, Jay McCarthy wrote: > > It is simpler t

Re: [racket-dev] colon keywords

dler > wrote: > > That's what I meant to be saying. And yes: stupid me to forget about > readtables! > > Robby > > > On Wed, Oct 14, 2015 at 7:31 AM, Alex Knauth wrote: >> Should we make this into a meta-language? >> >> #lang colon-kw racket >&

Re: [racket-dev] colon infix operator in syntax-parse ?

arse: syntax/parse)) (syntax->datum (stxparse:syntax-parse #'(define x 3) #:literals (rkt:define) [(rkt:define x:stxparse:id v:stxparse:expr) #'(define-values [x] v)])) Alex Knauth -- You received this message because you are subscribed to the Google Groups "Racket D

[racket-dev] Streams and stream printing

the lambda would be necessary. What are all these extra `make-streams` and `mcons`s around all the elements of the stream, even when they are not streams themselves? Also is there a reason why streams use this instead of promises? Alex Knauth > On Dec 21, 2015, at 6:22 PM, Alexis King wrote

[racket-dev] link: module mismatch error

ase level: 0 internal explanation: variable not provided (directly or indirectly) in: delay* Alex Knauth -- 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 emai

Re: [racket-dev] link: module mismatch error

a bug. I fixed a bug with similar symptoms a few weeks > ago, so maybe this one has a similar cause. How would I try it? > > At Sat, 2 Jan 2016 15:41:44 -0500, Alex Knauth wrote: >> Hello, >> >> I've been getting a weird `link: module mismatch` error. Normally, tho

Re: [racket-dev] link: module mismatch error

> On Jan 2, 2016, at 4:20 PM, Alex Knauth wrote: > > You could try it by checking out my delay-light branch from > https://github.com/AlexKnauth/racket/tree/delay-light > > I get the error when compiling pkgs/racket-test/tests/racket/promise.rkt > where it uses `delay*`

Re: [racket-dev] link: module mismatch error

Thank you! > On Jan 2, 2016, at 5:39 PM, Matthew Flatt wrote: > > Thanks! I think I have a repair, but I'm still testing before I push. > > At Sat, 2 Jan 2016 17:31:36 -0500, Alex Knauth wrote: >> >>> On Jan 2, 2016, at 4:20 PM, Alex Knauth wrote: >>&

Re: [racket-dev] Release Announcement for v6.4

avoid the > word "now". > ------ > Alex Knauth: > - Allow separate read and write contracts for box/c (67e3899272792c2e5) Does this work? Box contracts allow separate contracts for controlling reading from and writing to the box, which lets contracts

Re: [racket-dev] Windows 7 64bit Dr Racket Crash

When you open DrRacket from the command-line, does it print out an error message then? > On Mar 9, 2016, at 1:06 PM, Robby Findler wrote: > > Thanks. > > Robby > > On Wed, Mar 9, 2016 at 11:56 AM, Curtis Dutton wrote: >> It closes immediately with no error messages. Windows gives the standar

Re: [racket-dev] Release Announcement for v6.6

ctly. In some cases, this will produce contract errors in > programs that did not have errors before. Should this mention that it now generates a contract for the existing type as well? That's the specific thing that would confuse people who are used to cast only generating a contract f

Re: [racket-dev] change to the Guide: syntax-id-rules is confusing

+1 > On Jul 29, 2016, at 11:50 AM, Stephen Chang wrote: > > Would anyone object if I removed mention of syntax-id-rules from the > Guide (and added a "deprecated" warning in the reference)? > > I think the documentation should not give the impression that > syntax-id-rules is idiomatic Racket s

Re: [racket-dev] TR case-> inference

nteger String)) > (-> Integer (U Integer String))) This is a super-type of (-> (U Boolean Integer) (U Integer String)). It's a super-type because both (-> Boolean (U Integer String)) and (-> Integer (U Integer String)) are super-types. It's not equivalent un

Re: [racket-dev] Release Announcement for v6.7

> On Oct 15, 2016, at 8:39 AM, Vincent St-Amour > wrote: > > The release announcement sketch that I have so far is below. Please > mail me new items and/or edits. > > Please phrase announcements using complete sentences and avoid the > word "now". > ---

Re: [racket-dev] Release Announcement for v6.7

> On Oct 15, 2016, at 2:47 PM, Vincent St-Amour > wrote: > > On Sat, 15 Oct 2016 11:07:39 -0500, > Alex Knauth wrote: >>Typed Racket: >>- `Any` unsoundness follow-up? (typed-racket @ >>191ec136b6606ed63b8548c8493dba59104c60fb >>5

Re: [racket-dev] what predicate is true for syntax objects with lexical context, and false for those without?

Sent from my iPhone >> On Dec 2, 2016, at 1:26 PM, Matthew Butterick wrote: >> >> On Dec 1, 2016, 5:33 PM -0800, Matthew Flatt , wrote: >> >> Assuming that "without lexical context" means "no scopes"[*], I don't >> think there's a simpler way right now than walking through the syntax >> object

[racket-dev] Why doesn't call-with-deep-time-limit return the result?

? Within the current documentation it's right below `call-with-limits`, which does return the result. The current description does nothing to point out this difference. Alex Knauth -- You received this message because you are subscribed to the Google Groups "Racket Developers&

[racket-dev] Macros expanding to generics

g of the internal-id to gen:custom-write from the other file, how do I do this properly? Is the ambiguous binding error a sign that I'm getting closer? Is there any other way to introduce generic interfaces that would be more friendly to macros? (By the way, my last example of defining a

[racket-dev] require: namespace mismatch while dealing with syntax-local-value of a syntax property

t;) #'(void)]) ;; - (define-stuff x) (define-thing y x) I've tried variations on compiling first vs. running without compiling, and I've tried putting syntax-local-introduce both before putting things in a syntax property and after pulling things out of

Re: [racket-dev] require: namespace mismatch while dealing with syntax-local-value of a syntax property

`(define-syntax name > (make-variable-like-transformer >(syntax-property > #''thing > 'prop > #,(preservable-property->expression >(syntax-property #'stuff* 'prop)]) > > This wo

Re: [racket-dev] Details on in-editor macroexpansion in DrRacket?

> On May 14, 2018, at 12:42 AM, Colin Fleming > wrote: > > Hi all, > > I work on Cursive , which is an IDE for Clojure > code based on IntelliJ. I've spoken to several of you at various conferences > over the years. > > I'm interested in understanding better how t