[racket-dev] `define-serializable-struct` and the `deserialize-info...` export

2013-11-08 Thread Matthew Flatt
Currently, `(define-serializable-struct id )` expands to `(provide deserialize-info:id-v0)`. The `deserialize-info...` identifier needs to be exported to make things work, but the export is a hassle: the programmer doesn't care about it, it's not usually documented, re-exporting modules don't

[racket-dev] backwards incompatibility (was Re: `define-serializable-struct` and the `deserialize-info...` export)

2013-11-08 Thread Robby Findler
(I think it is okay.) But here's a chance for me to point out something I heard about in a conversation with Satnam Singh at OOPSLA about how Google works that it seems like would be a nice fit for us. Here's my adaptation to our world: when you push out what some might consider a change that

Re: [racket-dev] backwards incompatibility (was Re: `define-serializable-struct` and the `deserialize-info...` export)

2013-11-08 Thread Jay McCarthy
I agree On Fri, Nov 8, 2013 at 12:39 PM, Robby Findler ro...@eecs.northwestern.edu wrote: (I think it is okay.) But here's a chance for me to point out something I heard about in a conversation with Satnam Singh at OOPSLA about how Google works that it seems like would be a nice fit for us.

Re: [racket-dev] backwards incompatibility (was Re: `define-serializable-struct` and the `deserialize-info...` export)

2013-11-08 Thread Matthew Flatt
Yes. Even if (as in the future) the current ring-0 packages weren't all the same git repository, I'd certainly at least try building them with this change. I think that running all the tests in the same way that DrDr does is not yet easy, but I hope we're moving in the direction of making that

Re: [racket-dev] backwards incompatibility (was Re: `define-serializable-struct` and the `deserialize-info...` export)

2013-11-08 Thread Robby Findler
On Fri, Nov 8, 2013 at 7:13 PM, Matthew Flatt mfl...@cs.utah.edu wrote: Yes. Even if (as in the future) the current ring-0 packages weren't all the same git repository, I'd certainly at least try building them with this change. I think that running all the tests in the same way that DrDr

Re: [racket-dev] backwards incompatibility (was Re: `define-serializable-struct` and the `deserialize-info...` export)

2013-11-08 Thread Matthew Flatt
At Fri, 8 Nov 2013 19:18:10 -0600, Robby Findler wrote: On Fri, Nov 8, 2013 at 7:13 PM, Matthew Flatt mfl...@cs.utah.edu wrote: Yes. Even if (as in the future) the current ring-0 packages weren't all the same git repository, I'd certainly at least try building them with this change. I

Re: [racket-dev] backwards incompatibility (was Re: `define-serializable-struct` and the `deserialize-info...` export)

2013-11-08 Thread Robby Findler
On Friday, November 8, 2013, Matthew Flatt wrote: At Fri, 8 Nov 2013 19:18:10 -0600, Robby Findler wrote: On Fri, Nov 8, 2013 at 7:13 PM, Matthew Flatt mfl...@cs.utah.edujavascript:; wrote: Yes. Even if (as in the future) the current ring-0 packages weren't all the same git