I see. There is actually some debate about the proper behavior of `as`,
but I believe the conversions that it will currently apply are:
1. Between scalar types (e.g., int to i32 and vice versa)
2. Into an object type (from @T into @Trait)
3. Borrowing (@T or ~T into T)
4. Converting between
People seem to reimplement C++ compilers, despite there being an
enormous amount of complex just parsing it... that said, the trickiest
and least specified part of the type checker right now is probably the
type inferencing algorithm, which I hope we can overhaul for something
that is clearer or
People seem to reimplement C++ compilers,
despite there being an enormous amount of complex just parsing it
Realistically though, how many implementations are libre and complete
enough to actually build a C++ compiler?
On 13 September 2013 10:51, Niko Matsakis n...@alum.mit.edu wrote:
I don't know what the bug with the docs is, but in the meantime, you
can build without the docs by doing:
./configure --disable-docs
and then rebuilding.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
Being queer is not about a right to privacy; it is
I think its great that you are going to be working on this. A
comprehensive datetime library is very important. That said I have not
got any particular ideas or comments.
I have not used Joda time/JSR-310 but the docs look promising and lots
of people seem to recommend it.
Cheers
Gareth
Hello Bardur,
Thank you so much for the reference resource of JSR-310 and its design docs.
I looked over it briefly and it is indeed very valuable.
It was listed in the wiki page, but the link was to the former home of it.
I have updated it.
Since nobody has claimed this module, I will start
Additionally,
Be able to convert bya to mya ? http://en.wikipedia.org/wiki/Bya
The short scale is now commonly used, btw... but also need to deal with
this for conversions:
http://en.wikipedia.org/wiki/Long_and_short_scales
There should be a preference boolean for conversion output for short
On Fri, Sep 13, 2013 at 3:10 PM, Luis de Bethencourt
l...@debethencourt.com wrote:
Please, please, I would love more comments and ideas. Will start asking for
reviews once I have some code to show.
Joda-Time looks quite nice. My only desire from a datetime lib is
easy to use correctly.
I believe that it would be a good idea to ensure that the Rust datetime
library is a superset of the JS Date object and that it passes a port of
the EcmaScript tests.
Cheers,
David
On 9/13/13 9:40 PM, Gareth Smith wrote:
I think its great that you are going to be working on this. A
One idea and use case for Paleontologists and Geologists coming over to
Rust in droves... :-)
Generically, just be able to handle simple Geologic addition and
subtraction against an Epoch itself (reference date)
http://en.wikipedia.org/wiki/Epoch_(reference_date) using known
abbreviations.
And
2013/9/13 Luis de Bethencourt l...@debethencourt.com
Cool!
Great and awesome feedback. The summary is that Joda-Time is what we
should aspire to have.
My goal is to first cover the most common use cases, and as Corey says,
easy to use correctly.
After that I can start considering the
Hi all,
I've hit a wall with rustdoc_ng. It fails to build on Windows with
http://buildbot.rust-lang.org/builders/auto-win-32-opt/builds/1435/steps/compile/logs/stdio,
the error being:
note:
i686-pc-mingw32\stage1\bin\rustc\i686-pc-mingw32\bin\lib.o:fake:(.text+0x68373):
undefined reference to
That is a very interesting read.
We certainly should learn from the experiences of other languages. This
being a good example.
I will be revisiting the linked documents listed in this thread repeatedly.
Fortunately the issue he mentions about NULLs creating random bugs, is
taken care of by
On 09/14/2013 02:57 AM, Daniel Micay wrote:
On Fri, Sep 13, 2013 at 1:17 AM, Minh Do m...@minhdo.org
mailto:m...@minhdo.org wrote:
On 08/27/2013 12:43 AM, Minh Do wrote:
My name is Do Nhat Minh, currently a final year Computer
Science student at Nanyang Technological
This? https://github.com/mozilla/rust/issues/9055
Windows APIs use stdcall, which implies all apis are decorated as
_SetLastError@16, while cdecl APIs are decorated as _SetLastError.
Our rustc is wrong so it generates llvm IR with wrong calling convention.
And when gcc prints linke error, it
15 matches
Mail list logo
