On Sat, Sep 14, 2013 at 12:21 AM, Minh Do wrote:
> On 09/14/2013 02:57 AM, Daniel Micay wrote:
>
> On Fri, Sep 13, 2013 at 1:17 AM, Minh Do 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 Technolo
On Wed, Sep 11, 2013 at 8:50 AM, Corey Richardson wrote:
> On Wed, Sep 11, 2013 at 3:27 AM, Gregory Maxwell wrote:
>> Presumably before rust reaches a point of earth-shaking importance
>> there will be an second implementation which can compile the first
>> compiler, thus permitting this solution
On 9/17/13 4:34 AM, Gokcehan Kara wrote:
I haven't used Haskell much but I know a little bit of Scala. In Scala
you need to be explicit because generics are compiled once to run with
different types. As far as I understand, rust compiles different copies
for each type (monomorphizing?) just like
> (It may also be the case that I'm ignorant of what the best C++ tools today
> do, though I'm pretty sure that these drawbacks are consequences of core C++
> design.)
Recent versions of Clang and GCC have much better diagnostics for
template issues than compilers from a couple of years ago
but
On Tue, Sep 17, 2013 at 7:34 AM, Gokcehan Kara wrote:
> Hello,
>
> I have met rust a few days ago and let me pay my respects first for making
> such a powerful language. I really hope to succeed making some contribution
> in the upcoming days.
>
> I was reading the tutorial (http://static.rust-lan
On Tue, Sep 17, 2013 at 12:08 PM, Daniel Micay wrote:
> In addition to what others have mentioned, explicit bounds allow generics to
> be type-checked from the definition, rather than each instantiation. You
> know that *any* set of type parameters fulfilling the bounds listed in the
> API will co
Gokcehan (cc'ing rust-dev)-
Correct, rust generics are not Turing-complete. (To my knowledge; I
don't think we've written the termination proof for the type-checker
yet. :)
Cheers,
-Felix
On 17/09/2013 15:25, Gokcehan Kara wrote:
Felix, C++ template errors are indeed a joy(!) to deal with.
Felix, C++ template errors are indeed a joy(!) to deal with. I guess I also
would rather be explicit than to have cryptic error messages that are pages
long. You're also right about the absence of errors without the client code
which makes sense in a context of safety.
It was the first time I hear
Gokcehan-
My understanding is that C++, due to its policy of SFINAE [1], usually
provides error feedback after the template has been fully instantiated
and the fully instantiated version fails to compile. This can lead to
hard to debug compile-time failures.
Good compilers can help with diss
Hello,
I have met rust a few days ago and let me pay my respects first for making
such a powerful language. I really hope to succeed making some contribution
in the upcoming days.
I was reading the tutorial (http://static.rust-lang.org/doc/tutorial.html)
specifically the section 16.3 and I was wo
Hi Alex,
I too applied for the position and after reading through some of your
pull requests and comments mid-August I remember thinking to myself
"man, I hope that guy hasn't applied too" :P Your work is awesome!
Congratulations :)
Cheers,
Michael
On 16.09.2013 22:43, Alex Crichton wrote:
11 matches
Mail list logo
