I think the high-level answer is that you have to understand something
about details that aren't currently specified but nevertheless are how
things currently work and then make a test that will work when you
make those additional assumptions (and then keep it running in drdr so
you can tell when t
On 12/01/2012 07:05 PM, Neil Toronto wrote:
Ah. It prints #f for me when I have debugging info turned on in
DrRacket; otherwise I get #. Must be inlining keeping it
around or something.
The problem with either finalizers or weak boxes is that neither
provides enough guarantees. Finalizers are ne
Ah. It prints #f for me when I have debugging info turned on in
DrRacket; otherwise I get #. Must be inlining keeping it
around or something.
The problem with either finalizers or weak boxes is that neither
provides enough guarantees. Finalizers are never guaranteed to be run. A
weak box may
This prints #f for me.
#lang racket
(define (make-box-thing v)
(make-weak-box (λ (_) v)))
(define bx (make-box-thing 4))
(collect-garbage)
(weak-box-value bx)
And I guess that non-closure procedures are held onto by the modules
they are inside. This program prints #f for me, and it seems to
c
Honestly, because I was too rushed to try them before I had to leave
this morning. :D However, now that I have the chance, I've found that
Typed Racket doesn't support them. I can't add support using
`required/typed', because `Weak-Box' would have to be a polymorphic type.
Also, they don't see
Yes, what you describe is what we imagine "migrate" will do.
Jay
On Sat, Dec 1, 2012 at 4:10 PM, Eli Barzilay wrote:
> Yesterday, Matthew Flatt wrote:
>> I've been working with Jay on a few more changes:
>>
>> Specifying metadata
>> ---
>>
>> "METADATA.rktd" is being replaced wit
Yesterday, Matthew Flatt wrote:
> I've been working with Jay on a few more changes:
>
> Specifying metadata
> ---
>
> "METADATA.rktd" is being replaced with "info.rkt", which is written in
> the `setup/infotab' language as usual.
>
> Define `deps' for dependencies, like this:
>
How about using a weak box instead?
Robby
On Sat, Dec 1, 2012 at 11:45 AM, Neil Toronto wrote:
> I'm getting ready to push a change to math/array that fixes a memory leak.
> I've devised a test that I think will determine whether an array's procedure
> gets collected after the array is made stri
I'm getting ready to push a change to math/array that fixes a memory
leak. I've devised a test that I think will determine whether an array's
procedure gets collected after the array is made strict, but I don't
know whether it works only by accident. Here it is:
(define: collected? : (Boxof B
Thanks so much.
-Ian
- Original Message -
From: "Matthew Flatt"
To: "J. Ian Johnson"
Cc: "dev"
Sent: Saturday, December 1, 2012 10:29:13 AM GMT -05:00 US/Canada Eastern
Subject: Re: [racket-dev] splicing-syntax-parameterize and
syntax-parameter-value
Interesting problem. I almost gave
On 12/01/2012 04:23 AM, David Vanderson wrote:
http://docs.racket-lang.org/data/Orders_and_Ordered_Dictionaries.html
Towards the bottom of this page there is the following error:
> (datum-order (make-fish 'alewife) (make-fish 'sockeye))
make-fish: undefined;
cannot reference undefined identi
On Fri, Nov 30, 2012 at 7:09 PM, Matthew Flatt wrote:
> Version-specific installation
> -
> Not to speak too much on Jay's behalf, but I think he isn't convinced
> that the new default is right. If `--shared' is the default, then a
> `raco pkg update' could be enough to
Interesting problem. I almost gave up, but I think I've sorted it out
--- repair pushed.
At Thu, 29 Nov 2012 18:20:18 -0500 (EST), "J. Ian Johnson" wrote:
> Simpler example:
>
> (require racket/splicing racket/stxparam)
> (define-syntax-parameter f #f)
> (define x 0)
> ;; 0
> (syntax-parameterize
http://docs.racket-lang.org/data/Orders_and_Ordered_Dictionaries.html
Towards the bottom of this page there is the following error:
> (datum-order (make-fish 'alewife) (make-fish 'sockeye))
make-fish: undefined;
cannot reference undefined identifier
Is this intentional?
Thanks,
Dave
_
14 matches
Mail list logo