Hi,
I'm new to Rust, currently trying out a few simple tests to get a
handle on things.
I have a few questions about linked lists. I see there are two list
modules in extra, one for ~ pointers and one for @ pointers. (I'm
using the current trunk rather than 0.7 if that makes a difference.)
The i
On Wed, Aug 28, 2013 at 4:43 PM, Josh Matthews wrote:
> That's covered by
> https://github.com/mozilla/rust/issues/4363https://github.com/mozilla/rust/issues/4363
> in the issue tracker.
>
That one is a little bit different.
https://github.com/mozilla/rust/issues/3779 is actually the same
struct.
This is a known bug: https://github.com/mozilla/rust/issues/3779
The fix, which you probably realized, is to change Option to
Option<~Foo> or Option<@Foo>.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Being queer is not about a right to privacy; i
That's covered by
https://github.com/mozilla/rust/issues/4363https://github.com/mozilla/rust/issues/4363in
the issue tracker.
Cheers,
Josh
On 28 August 2013 19:39, Amitava Shee wrote:
> I am getting a Bus error - please see the following.Should I file this as
> an issue in github?
>
> amitava:
I am getting a Bus error - please see the following.Should I file this as
an issue in github?
amitava:learn amitava$ cat app.rs
// vi:ts=4:sw=4:nu
fn main() {
// should not compile - infinite size, needs redirection
struct Foo {
child: Option
};
let c = Foo {child: None};
Thank you for the advice. I will try my best on the documentation front. I
go by the name MrOrdinaire on #rust irc.
On Aug 28, 2013 1:36 AM, "Tim Chevalier" wrote:
> On Mon, Aug 26, 2013 at 9:43 AM, Minh Do wrote:
> > My name is Do Nhat Minh, currently a final year Computer Science student
> at
Thanks, I will look into cling for inspiration.
On Aug 28, 2013 1:46 AM, "Daniel Micay" wrote:
> On Tue, Aug 27, 2013 at 1:36 PM, Tim Chevalier
> wrote:
> >
> > There are only a few rusti bugs in the issue tracker --
> >
> https://github.com/mozilla/rust/issues?direction=desc&labels=A-rusti&mile
> From: Bill Myers
>
> I was reading a proposal about adding "datasort refinements" to make enum
> variants first-class types, and it seems to me there is a simpler and more
> effective way of solving the problem.
>
> The idea is that if A, B and C are types, then "A | B | C" is a
> "structural" e
I was talking about
http://smallcultfollowing.com/babysteps/blog/2012/08/24/datasort-refinements/,
which essentially introduces structural enums but only for variants belonging
to the same named enum.
> * This strikes me as an extreme change to the language, but
perhaps my gut is o
The issues in O'Caml seem to be due to the fact that in O'Caml function
parameter and return types are inferred, and thus "accidentally oversized" enum
types can propagate through them.
In Rust, they must specified by the user, so those oversized enum types will
cause an error as they are passe
See this mailing list thread for background:
https://mail.mozilla.org/pipermail/rust-dev/2013-June/004545.html
On Wed, Aug 28, 2013 at 2:38 PM, Corey Richardson wrote:
> On Wed, Aug 28, 2013 at 8:34 AM, Benjamin Striegel
> wrote:
> > See here:
> >
> > http://www.cs.virginia.edu/~evans/cs4414-f
On Wed, Aug 28, 2013 at 8:34 AM, Benjamin Striegel
wrote:
> See here:
>
> http://www.cs.virginia.edu/~evans/cs4414-fall2013/pages/ps1.html
>
> Strikes me as a bit of a bad idea
I don't think it's a bad idea, but it's definitely going to be
challenging. I think it's exciting!
> Perhaps we should
See here:
http://www.cs.virginia.edu/~evans/cs4414-fall2013/pages/ps1.html
Strikes me as a bit of a bad idea, but I'll give the professor points for
audacity. Apparently they're mandating 0.7. Perhaps we should reach out and
offer support to the students? If we can establish a relationship, it co
Bill (cc'ing rust-dev)-
[Executive summary: the provided proposal needs further work.]
I do not know which discussion of data sort refinements you had been
reading; I would have liked context about where you were coming from. I
assume it was either Niko's blog post [1] or issue #1679 [2], but
14 matches
Mail list logo
