On Sun, Jul 7, 2013 at 11:44 AM, Carl Eastlund wrote:
> It seems to me our new package system runs into trouble if two people write
> packages that use the same connection name. Let's say we have two packages,
> alice-tree and bob-tree, both of which provide the collection
> data/red-black-tree,
At Sun, 7 Jul 2013 13:42:22 -0400, Sam Tobin-Hochstadt wrote:
> On Sun, Jul 7, 2013 at 1:26 PM, wrote:
> >
> > | Finally, `racket/base' provides the new function
> > | `call-with-default-reading-parameterization', which is used to guard
> > | various file `read's to make them consistent and avoid
It seems to me our new package system runs into trouble if two people write
packages that use the same connection name. Let's say we have two
packages, alice-tree and bob-tree, both of which provide the collection
data/red-black-tree, but both provide different interfaces (perhaps similar
function
On Sun, Jul 7, 2013 at 1:26 PM, wrote:
>
> | Finally, `racket/base' provides the new function
> | `call-with-default-reading-parameterization', which is used to guard
> | various file `read's to make them consistent and avoid security holes.
It looks like `call-with-default-reading-parameterizat
The change I made was the minimum delta to make the tests run in DrDr,
since the files already had a `main` submodule which ran the actual
tests.
Sam
On Sun, Jul 7, 2013 at 4:42 AM, Robby Findler
wrote:
> Raco test runs the file if there is not test sub module. Fwiw.
>
>
> On Saturday, July 6, 2
Raco test runs the file if there is not test sub module. Fwiw.
On Saturday, July 6, 2013, Eli Barzilay wrote:
> It doesn't make much sense to use a test submodule in files that are
> intended to be (only) tests.
>
>
> Earlier today, Robby Findler wrote:
> > That's the plan. Thanks for fixing them
6 matches
Mail list logo