Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-30 Thread Robby Findler
I like the last sentence of Sam's latest bullet. Robby On Thursday, October 30, 2014, Matthias Felleisen wrote: > > On Oct 30, 2014, at 3:45 PM, Sam Tobin-Hochstadt > wrote: > > >> > >> How about this one? (Starting from Matthias's offering and editing the > >> apology from Sam's a bit.) > >>

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-30 Thread Matthias Felleisen
On Oct 30, 2014, at 3:45 PM, Sam Tobin-Hochstadt wrote: >> >> How about this one? (Starting from Matthias's offering and editing the >> apology from Sam's a bit.) >> >> Typed Racket closes a safety hole in the typing for the >> exception system. The revised type system restricts raise so >>

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-30 Thread Sam Tobin-Hochstadt
On Wed, Oct 29, 2014 at 9:46 PM, Robby Findler wrote: > I don't think that "it's true of every type system everywhere" is a > good rationale for not owning backwards-incompatible changes (even > when they are "good" backwards incompatible changes, as this one > certainly is). I do agree with you,

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Robby Findler
I don't think that "it's true of every type system everywhere" is a good rationale for not owning backwards-incompatible changes (even when they are "good" backwards incompatible changes, as this one certainly is). I do agree with you, however, that what is especially bad is requiring changes to "w

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Sam Tobin-Hochstadt
On Wed, Oct 29, 2014 at 6:57 PM, Matthias Felleisen wrote: > > properly -> corresponding fashion? No, it's a different change (the one I numbered 1. in my first message). Sam > > Otherwise fine > > > On Oct 29, 2014, at 6:54 PM, Sam Tobin-Hochstadt wrote: > >> On Wed, Oct 29, 2014 at 6:42 PM,

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Matthias Felleisen
properly -> corresponding fashion? Otherwise fine On Oct 29, 2014, at 6:54 PM, Sam Tobin-Hochstadt wrote: > On Wed, Oct 29, 2014 at 6:42 PM, Matthias Felleisen > wrote: >> >> 1. Can we please, pretty please, drop these "now"s from every single >> sentence? >> >> 2. I think this is close

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Sam Tobin-Hochstadt
On Wed, Oct 29, 2014 at 6:42 PM, Matthias Felleisen wrote: > > 1. Can we please, pretty please, drop these "now"s from every single sentence? > > 2. I think this is close to what we may wish to say. Here is a small edit: > > * Typed Racket closes a safety hole due to the types for the > exceptio

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Matthias Felleisen
1. Can we please, pretty please, drop these "now"s from every single sentence? 2. I think this is close to what we may wish to say. Here is a small edit: * Typed Racket closes a safety hole due to the types for the exception system. The revised type system restricts raise so that only ins

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Sam Tobin-Hochstadt
Here's another idea: * To ensure safety, Typed Racket now prohibits raising any values other than exns and simple flat data. Some existing programs may now have type errors because of this. Sam On Wed, Oct 29, 2014 at 6:12 PM, Sam Tobin-Hochstadt wrote: > The reason I don't like the second sent

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Sam Tobin-Hochstadt
The reason I don't like the second sentence you wrote is that it's true of every type system everywhere. And also, the more significant change for users will almost certainly be the first one (it's required changes to several packages already) -- almost no one raises anything that isn't an exn, and

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Sam Tobin-Hochstadt
On Wed, Oct 29, 2014 at 5:47 PM, Robby Findler wrote: > Yes, that's what I mean. I don't think that the sentence "This may > break existing programs that rely on unsafe behavior." is accurate. > How about "This may break existing programs." or "Closing this hole > requires us to disallow some prog

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Robby Findler
I prefer the second sentence I sent to either of those. Fundamentally I think it is reasonable for the sentence to be slightly apologetic. There was a problem, we fixed it, but the fix may require some pain of our users. There's nothing wrong with that; it's just a fact of life. No shame in hiding

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Robby Findler
Yes, that's what I mean. I don't think that the sentence "This may break existing programs that rely on unsafe behavior." is accurate. How about "This may break existing programs." or "Closing this hole requires us to disallow some programs that do not signal runtime errors." or something like that

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Sam Tobin-Hochstadt
There were two holes. 1. We allowed exception handlers to assume that they received values of type `exn`, even when that wasn't right. 2. We allowed typed programs to throw arbitrary values, which means that you could throw a typed function to an untyped handler, which could then misuse it. Both

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Robby Findler
Sam: can you elaborate on precisely what the hole was? In particular, if there are any safe programs that the type system now rejects, I'd be in favor of a slightly different wording. Robby On Wed, Oct 29, 2014 at 2:35 PM, Sam Tobin-Hochstadt wrote: > On Wed, Oct 29, 2014 at 3:30 PM, Ryan Culpep

[racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Ryan Culpepper
The release announcement sketch that I have so far is below. Please mail me new items and/or edits. -- Racket version 6.1.1 is now available from http://racket-lang.org/ * Mac OS X Yosemite: fixed compatibility problems, m

Re: [racket-dev] Release Announcement for v6.1.1, Second Draft

2014-10-29 Thread Sam Tobin-Hochstadt
On Wed, Oct 29, 2014 at 3:30 PM, Ryan Culpepper wrote: > > * Exception handling changed to be safe. This may break existing > programs that rely on unsafe behavior. > > * Casts and predicates are supported in typed regions. I think these two bullets (esp the first one) need to make clear that t

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

2014-10-27 Thread Neil Toronto
On 10/27/2014 12:25 PM, Ryan Culpepper wrote: neil: - remove dependence on libgtkgl (c601b82f) * For OpenGL on Linux, removed dependence on libgtkgl and added support for core profiles (see `set-legacy?`). Neil ⊥ _ Racket Developers list: http://lists.racket-l

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

2014-10-27 Thread Vincent St-Amour
For TR: * Exception handling changed to be safe. This may break existing programs that rely on unsafe behavior. * Exports from the GUI and framework libraries have types, and can be used transparently from typed programs. * Casts and predicates are supported in typed regions. Vincent At

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

2014-10-27 Thread Robby Findler
For me: * Added the drracket/check-syntax library to facilitate check syntax-like behavior in other IDEs * Redex: explained the benchmark programs added a conditional-form to metafunctions * 2htdp/image's notion of equality no longer considers an image's baseline. * Contracts: contract-

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

2014-10-27 Thread Matthew Flatt
At Mon, 27 Oct 2014 12:25:22 -0400, Ryan Culpepper wrote: > mflatt: > - optimizations (most from Gustavo Massaccesi) (82ffd405, 25c05d66, > a7a912ee, 1f2f7a1d, d14b4a80, 769c5b6e, 35eb6562, 15423988) > - add replace-evt (as suggested by Jan Dvořák) (bc69a9b0) > - fixing letrec updates? (e

[racket-dev] Release Announcement for v6.1.1

2014-10-27 Thread Ryan Culpepper
The release announcement sketch that I have so far is below. Please mail me new items and/or edits. -- mflatt: - optimizations (most from Gustavo Massaccesi) (82ffd405, 25c05d66, a7a912ee, 1f2f7a1d, d14b4a80, 769c5b6e, 35eb6