Hi everyone,
There is currently a feature whereby custom enum variant discriminants
can be specified:
pub enum Foo {
Bar = 1,
Baz = 2,
Boo = 3,
}
The sole use of this is casting from the enum to an int:
println(fmt!("%d", Bar as int)); // prints 1
This
Forgot to reply-all. d'oh!
Regards,
Paul Nathan
Sent from my iPhone
On Feb 28, 2013, at 11:01 AM, Paul Nathan wrote:
> I would suggest a three-ring strategy.
>
> 1. Compiler and minimal libs, much like C. This is the sacred system
> maintained by rust devs. This is just what would be needed
On 28/02/2013 10:50 AM, Graydon Hoare wrote:
> get away with doing this (in libstd):
>
> #[vers="1.0.0"]
> pub mod foo = "github.com/user/foo#1.0";
>
> #[vers="1.1.0"]
> pub mod foo = "github.com/user/foo#2.0";
Also note: in case this sounds too terrifying in
On 28/02/2013 9:43 AM, Erick Tryzelaar wrote:
> Hello Tommy,
>
> I feel our process will ultimately be more along the lines of a small
> standard library that needs hooks into the compiler and runtime, and an
> extensive CPAN-esque repository for everything else. We'll have first
> party "blessed"
Hello Tommy,
I feel our process will ultimately be more along the lines of a small
standard library that needs hooks into the compiler and runtime, and an
extensive CPAN-esque repository for everything else. We'll have first party
"blessed" packages for things like a web client, compression, and h
On 02/22/2013 07:07 PM, Graydon Hoare wrote:
> After some consultation with the rest of the core rust developer group,
> I've posted some new guidelines concerning editing rust's libraries:
>
>https://github.com/mozilla/rust/wiki/Libs
>https://github.com/mozilla/rust/wiki/Library-editing
Thank you for pointing out. I didn't know po4a, so I made pomarkdown
myself. I agree that po4a is more appropriate in this task.
I do plan to maintain internationalized documents. Furthermore, I aim at
the
eventual inclusion of internationalized documents in the build process if
the community agree
On 27/02/2013 10:38 PM, Cha, Hojeong wrote:
> Hello everyone,
>
> I think many developers have an interest in learning Rust via tutorial.
> But the current tutorial is written in English, so it precludes many
> potential developers which English is not his/her native language.
>
> So I thought
Thank you for pointing out. I didn't know po4a, so I made pomarkdown
myself. I agree that po4a is more appropriate in this task.
I do plan to maintain internationalized documents. Furthermore, I aim at
the formal inclusion of internationalized documents in the build process if
the community agrees
Cha, Hojeong wrote:
> So I thought that it would be beneficial to internationalize Rust
> documents, or at least have a base-level work for
> internationalization.
>
> https://gist.github.com/karipe/330d1ce1f0dbbf67abf0#file-tutorial_ko-md
>
> I would like to hear your opinions about this way o
10 matches
Mail list logo
