or the set of values
that would pass the contracts or something like that.
On Jan 30, 2015, at 12:30, Alexander D. Knauth alexan...@knauth.org wrote:
On Jan 30, 2015, at 1:53 PM, Alexis King lexi.lam...@gmail.com wrote:
No, it doesn’t need to be wrapped in an opaque structure. Wrapping
.
On Jan 30, 2015, at 07:27, Alexander D. Knauth alexan...@knauth.org wrote:
On Thu, Jan 29, 2015, at 09:03 PM, Alexis King wrote:
It isn’t wrapped in an opaque structure. That wasn’t a part of my proposal,
and while I didn’t think of it until you brought it up, I still think it’s
unnecessary
(: b : (Boxof Number))
(define b (box 1))
(set-box! (cast b (Boxof (U Number String))) I am a string)
(ann (unbox b) Number) ;I am a string” ; not a contract error
On Jan 29, 2015, at 20:20, Alexander D. Knauth alexan...@knauth.org wrote:
Furthermore, even if the wrappers were shared between
Um, for this:
(module typed typed/racket/base
(provide (struct-out Foo))
(struct [A] Foo ([x : A] [y : A]) #:transparent))
(Foo a 'b)
Should be fine because Foo could be instantiated at the type (U String Symbol).
On Jan 29, 2015, at 9:25 PM, Alexis King lexi.lam...@gmail.com wrote:
I
Furthermore, even if the wrappers were shared between functions, untyped code
would recieved wrapped values, which would render them quite useless.
If it’s not an opaque type, but something like a list, then this works, and the
untyped code receiving wrapped values isn’t a problem here:
#lang
There’s a bug report about this here:
http://bugs.racket-lang.org/query/?cmd=viewpr=14524
Though I notice it gives a different error message now.
But why should structure type declarations being a module-wide construct?
Internal function definitions work, and internal type definitions work, so why
But I think it’s important that it doesn’t use gensym or something like that,
it uses syntax-marks, which means you can break these lexical scoping rules if
you want/need to by using either syntax-local-introduce or datum-syntax:
#lang racket
(require syntax/parse/define)
(define-simple-macro
In terms of bugs, it’s probably related to this problem with call-with-values
and poly-dots:
#lang typed/racket
(: f : (All (a ...) [(- (values Any ... a)) - Void]))
(define (f g)
(call-with-values g void))
;=
. . ../../Applications/Racket
the `racket/racket3m` process
from the outside. For example, the process may have exceeded a
memory-use limit.
At Sat, 19 Jul 2014 20:25:24 -0400, Alexander D. Knauth wrote:
I made a fork of the racket repo and committed some changes in a topic
branch,
but I got this:
make[8]: Leaving
I made a fork of the racket repo and committed some changes in a topic branch,
but I got this:
make[8]: Leaving directory
`/home/travis/build/AlexKnauth/racket/racket/src/build'
make[7]: Leaving directory
`/home/travis/build/AlexKnauth/racket/racket/src/build'
make[6]: Leaving directory
10 matches
Mail list logo