Re: [racket-dev] colon keywords

2015-10-13 Thread Neil Van Dyke
Alexis King wrote on 10/14/2015 01:32 AM: I think that Racket 6.3 would be a great time to make `:abc` read the same as `#:abc`. This sounds like an incredibly breaking change. It should not be a breaking change. Anyone who has used a colon as a leading character in a symbol (other than the

Re: [racket-dev] colon keywords

2015-10-13 Thread Alexis King
> I think that Racket 6.3 would be a great time to make `:abc` read the same as > `#:abc`. This sounds like an incredibly breaking change. I support it in general, I think, but it seems like another feature that makes sense for Racket 2/Remix/whatever it ends up being called. I’m sure there are

[racket-dev] colon keywords

2015-10-13 Thread Neil Van Dyke
I think that Racket 6.3 would be a great time to make `:abc` read the same as `#:abc`. For those of us who are pained deeply by `#:abc`, being able to use `:abc` would be a big aesthetic improvement for Racket. Neil V. -- You received this message because you are subscribed to the Google Gro

Re: [racket-dev] marking stuff deprecated in documentation

2015-10-13 Thread Sam Tobin-Hochstadt
The warning is generated by `deprecated`, from `scribble/manual`. Sam On Tue, Oct 13, 2015 at 3:50 PM, Alexis King wrote: >> I'm curious to know the answer to Alexis' question: Semantics aside, >> how do I simply make something with a standard warning appearance? In >> many cases that's probabl

Re: [racket-dev] marking stuff deprecated in documentation

2015-10-13 Thread Alexis King
> I'm curious to know the answer to Alexis' question: Semantics aside, > how do I simply make something with a standard warning appearance? In > many cases that's probably sufficient. I went looking for examples of > this in the docs, so I could go look for its Scribble. But I couldn't > find any

Re: [racket-dev] marking stuff deprecated in documentation

2015-10-13 Thread Greg Hendershott
Oh then maybe I'm misunderstanding "deprecated". I was thinking of it from the narrow/selfish point of view of a (new system) package developer. In that system, deprecated can't mean "will be removed soon", because you can't ever remove things from a package. (Packages are supposed to be backward

Re: [racket-dev] marking stuff deprecated in documentation

2015-10-13 Thread Vincent St-Amour
Someone correct me if I'm wrong, but my understanding is that, in the context of Racket at least, "deprecated" implies that we will be removing that code in the near-ish future. As we recently did for, e.g., class100. My understanding is also that we don't want to remove things like mzscheme, mzli