At Wed, 21 Jan 2015 11:22:38 -0500, Tony Garnock-Jones wrote:
Over the past few months, more and more subsystems have started logging
at info level as part of regular compilation.
I prefer having PLTSTDERR=info in order to catch log-info that happens
at runtime, and find the compile-time log
I don't think you want to do anything with the compiler or macros.
Instead, it's a matter of having a sufficiently powerful inspector
(which is the concept of inspectability turned into a language
construct).
If you have just
(struct a (x))
(a 1)
then the result will print as `#a`. But if you
This program returns #f - I was expecting to see #t.
#lang racket
(define a '(1 2 3))
(define b '(1 2 3))
(eq? a b)
Why not guarantee uniqueness of literals occurring in the same module?
/Jens Axel
_
Racket Developers list:
Hi Matthew,
Thanks for those thoughts.
On 01/22/2015 09:11 AM, Matthew Flatt wrote:
On 1 above: I've been uncertain of the best way to organize logging
from the start, but the idea of grouping topics hierarchically (such as
a compilation topic group) doesn't sound promising.
I agree. Better
Simple enough. This works:
#lang racket
(define (make-me-a-struct)
(struct foo ())
(foo))
(make-me-a-struct) ; = #foo
This does not:
#lang typed/racket
(define (make-me-a-struct)
(struct foo ())
(foo)) ; error: cannot apply a function with unknown arity
(make-me-a-struct)
This
5 matches
Mail list logo
