nice!
2014年12月8日 上午5:27于 "Daniel Trstenjak" 写道：
>
> Hi all,
>
> https://github.com/dan-t/rusty-tags
>
> Have fun!
>
>
> Greetings,
> Daniel
> ___
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
__
Could you show us the memory layout of Box? Thank you!
2014年5月21日 上午6:59于 "Daniel Micay" 写道：
> On 20/05/14 06:45 PM, Masanori Ogino wrote:
> > Hello.
> >
> > I found that the Reference Manual uses the term "owning pointer", the
> > Pointer Guide and liballoc do "owned pointer" and Tutorial does "
It's easy to submit a pull request, for a git programmer. My difficulty is
the weak of English level to write a so long rfc.
2014年4月23日 上午5:57于 "Tommi" 写道：
> On 2014-04-22, at 21:44, Brian Anderson wrote:
>
> I'm not sure what you are asking for here. Have you submitted this as a
> pull request t
Along with the "A 30-minute intro to Rust", we also need a 1-minute and/or
5-minute intro, in rust-lang.org website.
2014年4月22日 上午7:11于 "Brian Anderson" 写道：
> Hi.
>
> I've been convinced recently that Rust is missing crucial documentation of
> a particular nature: using Rust in practice. I would l
test result: FAILED. 2 passed; 1387 failed; 50 ignored; 0 measured
what happens?
Most tests failed at 'explicit failure':
[run-pass] run-pass/unwind-unique.rs stdout
error: test run failed!
command:
PATH="i686-pc-mingw32/stage2/bin/rustlib/i686-pc-mingw32/lib;;.;D:\Min
Zero is a bad name here, it should be renamed or removed
2014年4月9日 上午1:20于 "Kevin Ballard" 写道：
> On Apr 7, 2014, at 1:02 AM, Tommi Tissari wrote:
>
> On 07 Apr 2014, at 08:44, Nicholas Radford
> wrote:
>
> I think the original question was, why does the zero trait require the add
> trait.
>
> If
+1 for printf! and printfln!
2014年4月3日 下午1:14于 "Daniel Micay" 写道：
> Perhaps we should have `print` and `println` back in the prelude and
> call these `printf!` and `printfln!`. I think it would be a lot clearer,
> as people always ask how these are different from `print` and `println`.
>
>
> _
+1
2014年3月24日 上午5:46于 "Patrick Walton" 写道：
> On 3/23/14 2:19 PM, Ziad Hatahet wrote:
>
>> You wouldn't probably use this for each and every method, but what it
>> gives you is Go-style duck typing.
>>
>> Sure you can define a trait, but what if the struct you to pass to your
>> function does not i
IMO, this is bad.
2014年3月23日 下午6:34于 "Ziad Hatahet" 写道：
> Hi all,
>
> Are there any plans to implement structural typing in Rust? Something like
> this Scala code: http://en.wikipedia.org/wiki/Duck_typing#In_Scala
>
>
> ___
> Rust-dev mailing list
> Rust
Great news!
2014年3月18日 上午9:27于 "Yehuda Katz" 写道：
> Hello Rustlers,
>
> I'll be writing here more with more details soon. For now, a few quick
> comments:
>
>- I'm really glad that Mozilla and the Rust team are prioritizing
>package management. An open source language ecosystem really lives
Github has itself email notification which I'm using.
2014年3月15日 上午5:48于 "Brian Anderson" 写道：
> I suspect this will not impact many, but I'm shutting down the
> rust-commits mailing list, which was just used to relay commits via the
> GitHub commit hook.
>
> I haven't been subscribed to it for a l
"glob use" just make compiler loading more types, but make programmers a
lot easy (to write, to remember). perhaps I'm wrong? thank you!
--
by *Liigo*, http://blog.csdn.net/liigo/
Google+ https://plus.google.com/105597640837742873343/
___
Rust-dev mail
Hey Rusties:
Could we remove the one in `rustlib`, and let `rustc` reuse the one in
'/usr/local/lib'?
If we could do this, the distribution package will be much smaller.
`rustc` is run only in host environment, right?
(Another option, static link rustc, and remove all *.so in rustlib.)
Liigo.
__
Hi Rustist:
I can't find any information for that in the wiki page:
https://github.com/mozilla/rust/wiki/Meetings
--
by *Liigo*, http://blog.csdn.net/liigo/
Google+ https://plus.google.com/105597640837742873343/
___
Rust-dev mailing list
Rust-dev@moz
*((int*)0): In theory, this is memory unsafe; In practical, this has been
exist for about thirty years, making many software system crash. But I
know, most C++ programmers don't consider it a big deal.
2014-03-06 13:06 GMT+08:00 comex :
> On Wed, Mar 5, 2014 at 11:42 PM, Patrick Walton
> wrote:
ou read about that?
>
> I'm explaining about the extended usage of two languages, one like main
> language and the other one like scripting.
>
> El 05/03/14 11:17, Liigo Zhuang escribió:
>
>> I do known what I need. You are not me, please not tell me what need to
f you can't be civil, then ignore the thread and move
> on.
>
>
> On Tue, Mar 4, 2014 at 11:40 PM, Liigo Zhuang wrote:
>
>> If I select Rust as my main language, I don't think I have any reason to
>> write new code in Go. Go away!
>> 2014年3月5日 上午3:44于 &quo
common the usage of Lua for scripting
>
> El 05/03/14 04:40, Liigo Zhuang escribió:
>
>> If I select Rust as my main language, I don't think I have any reason to
>> write new code in Go. Go away!
>>
>> 2014年3月5日 上午3:44于 "John Mija" > <mailto:jon
If I select Rust as my main language, I don't think I have any reason to
write new code in Go. Go away!
2014年3月5日 上午3:44于 "John Mija" 写道：
> Every time there is a new language, developers have to start to developing
> from scratch the same algorithms.
> The alternative has been to use C libraries a
I like this
2014年3月2日 上午4:07于 "Niko Matsakis" 写道：
> On Fri, Feb 28, 2014 at 11:23:23PM -0800, Kevin Ballard wrote:
> > I'm also slightly concerned that #[deriving(Data)] gives the
> > impression that there's a trait Data, so maybe that should be
> > lowercased as in #[deriving(data)], or even just
s no obvious vendor, shows up a lot in linux
> triples, though `x86_64-pc-linux-gnu` is also common; "-gnu" probably means
> the target has a GNU userspace.
>
>
> On 02/14/2014 05:16 PM, Liigo Zhuang wrote:
>
> Hello Rusties:
>
> I'm using Debian 7.4 Linux, no
of the parts separated by dashes)
> have a specific order and meaning, so they can't just be randomly rephrased
> on a per-combination basis.
>
> They're not meant to be pretty English, but to encode information in a
> semi-readable format.
> On 15 Feb 2014 01:31, &quo
2014-02-15 9:26 GMT+08:00 Lee Braiden :
> Unknown-linux presumably means generic linux, and GNU you should probably
> learn about, fir your own good, at gnu.org especially gnu.org/philosophy.
>
> Hint: much of what people think of as "Linux" is actually part of GNU, or
> using GNU.
>
If so, why no
Hello Rusties:
I'm using Debian 7.4 Linux, not "unknown linux" obviously.
And I don't know the meaning of `-gnu`.
On Windows, that it `x86-pc-mingw32`, which is quite meaningful to
understand.
Thank you.
--
by *Liigo*, http://blog.csdn.net/liigo/
Google+ https://plus.google.com/10559764083774
I'm very sorry. I forgot `make install`. Now it works OK.
2014-02-14 11:58 GMT+08:00 Liigo Zhuang :
> rustc -v:
> ```
> rustc 0.10-pre (a102aef 2014-02-12 08:41:19 +0800)
> host: x86_64-unknown-linux-gnu
> ```
>
> The most recent rustc, i just recompiled from m
of `rustc -v`? The snippet complies ok for
> me off master.
>
> On Thu, Feb 13, 2014 at 8:17 AM, Liigo Zhuang wrote:
> > I compiled the lasted rustc from source yesterday.
> >
> > 2014年2月13日 下午8:17于 "Alex Crichton" 写道：
> >
> >> What version
I compiled the lasted rustc from source yesterday.
2014年2月13日 下午8:17于 "Alex Crichton" 写道：
> What version of the compiler are you using? The clone-able Chan only
> very recently landed, so you'll need a very up-to-date compiler to get
> the change.
>
> On Thu, Feb 13,
Hi Rusties,
When try to compile tmp.rs, I got the error:
```
tmp.rs:8:10: 8:19 error: type `std::comm::Chan` does not implement any
method in scope named `clone`
tmp.rs:8 let _ = c.clone();
^
```
But I don't know how to do. Please help me. Thank you.
tmp.rs:
```
#[deriv
2014年2月9日 上午7:35于 "Alex Crichton" 写道：
>
> We do indeed want to make common tasks like this fairly lightweight,
> but we also strive to require that the program handle possible error
> cases. Currently, the code you have shows well what one would expect
> when reading a line of input. On today's mas
:pipe()" is better,
> but since function names are often verbs or start with verbs, it implies
> not that a pipe is being built, but that the function accepts something
> that is piped through the channel.
>
> Channel::new_pipe() returning a (Source, Sink) seems ideal. "new
let tuple = (1.0f32, 2.0f32, 3.0f32, 4.0f32);
let a,b,c = tuple.1, tuple.2, tuple.3; // I prefer this. (0-based?)
// or: tuple.a, tuple.b, tuple.c, ...z
// or: tuple[index]
2014/1/15 Richard Diamond
> Basically the idea here is to support shuffling for SIMD types in a way
> that can be easily l
People should rethink the Chan api that Chan::new() does not returns a
value of type Chan (instead, a tuple), which is strange, and inconsistent
with other Type::new().
2014/1/14 Brian Anderson
> In light of the general consensus that unbounded channels are not so hot,
> here's a new proposal f
Great work, thanks.
在 2014年1月10日 上午5:04，"Brian Anderson" 写道：
> Mozilla and the Rust community are pleased to announce version 0.9 of the
> Rust compiler and tools. Rust is a systems programming language with a
> focus on safety, performance and concurrency.
>
> This was another eventful release i
Code full of .unwrap() is not good smell I think.
在 2013年12月24日 上午4:42，"Simon Sapin" 写道：
> FYI, made a pull request according to this proposal:
>
> https://github.com/mozilla/rust/pull/11129
>
> --
> Simon Sapin
> ___
> Rust-dev mailing list
> Rust-dev@m
I like Iter suffix, short, and say what it is.
在 2013年12月21日 下午12:51，"Palmer Cox" 写道：
> I noticed recently that there seem to be 3 distinct Iterator naming
> conventions currently in use:
>
> 1. Use the "Iterator" suffix. Examples of this are SplitIterator and
> DoubleEndedIterator.
> 2. Use the "
013-12-17
>
>
> On 12/16/2013 06:41 PM, Liigo Zhuang wrote:
>
>
> 2013/12/16 Brian Anderson
>
>> My feeling is that it is a crate, since that's the name we've
>> historically used. There's already been agreement to remove "extern mod" i
2013/12/16 Brian Anderson
> My feeling is that it is a crate, since that's the name we've
> historically used. There's already been agreement to remove "extern mod" in
> favor of "crate".
>
IMO, "package" is used in several languages, maybe it's much familiar and
friendly to rust newbies:
> `
Rust compiler compiles "crates", rustpkg manages "packages".
When develope a library for rust, I write these code in lib.rs:
```
#[pkgid = "whoami"];
#[crate_type = "lib"];
```
Note, I set its "package" id, and set its "crate" type, and it is compiled
to an .so library. Now please tell me, wh
2013/12/14 Corey Richardson
> Packages don't really exist as a concept at all. Supposedly `rustpkg`
> deals with "packages" but in reality, it just deals with crates.
>
> And they're certainly not part of the module system.
2013/12/14 György Andrasek
> O
What is the distinction of package and crate in Rust?
2013/12/14 Patrick Walton
> On 12/13/13 4:56 PM, Liigo Zhuang wrote:
>
>> "package" and "module", we only need one. Most other language only have
>> one. The more, the more complicate.
>>
>&
"package" and "module", we only need one. Most other language only have
one. The more, the more complicate.
libstd.so: What we call it? "library" "package" "crate"?? other language
usually call it "library".
std::io::fs: We call it "module", other language usually call it "package"
or "module".
S
looks like a good idea.
I always think "extern mod extra" is repetitious, because, when i "use
extra::Something", the compiler always know I'm using the mod "extra".
2013/12/13 Piotr Kukiełka
> Hi all,
>
> I'm new to rust but I'm quite interested in learning it more deeply and
> contributing t
Is do-notation in Haskell similar as: try{ block } ?
2013/12/7 Huon Wilson
> On 07/12/13 12:08, Jordi Boggiano wrote:
>
>> On Sat, Dec 7, 2013 at 2:01 AM, spir wrote:
>>
>>> On 12/07/2013 01:12 AM, Gaetan wrote:
>>>
I am in favor of two version of the api: from_str which has already done
+1
在 2013年12月4日 上午5:58，"Gaetan" 写道：
> Sorry but that is a pretty bad answer. You cannot tell people to change
> their favorite email client just for rust-dev.
>
> You cannot do the same with you client, just because each one will have to
> set its own set of rules to tag, ...
>
> Gmail is a pretty
great work
2013/12/1 Corey Richardson
> Welcome to another issue of *This Week in Rust*, a weekly newsletter
> summarizing Rust's progress and community activity. As always, if you have
> something you'd like to be featured, just [send me an
> email](mailto:co...@octayn.net?subject=This Week in
在 2013年11月19日 下午8:44，"Daniel Micay" 写道：
>
> On Tue, Nov 19, 2013 at 7:35 AM, spir wrote:
> >
> > If this is all true, that recursive structures are the main, "almost the
> > only use case" of ~ pointers, then the tutorial is in my view rather ok
on
> > this point. But then, why does it seem there
在 2013年11月19日 下午8:41，"Gaetan" 写道：
>
> I think this is precisely one of the bigest issue, from a newbee point of
view. And I agree with spir on this point. It's not that important, but you
end up placing them everywhere "to make the compiler happy".
>
> ~str should be a ~T. If it is not, it should u
在 2013年11月19日 下午8:35，"spir" 写道：
>
> On 11/19/2013 12:51 PM, Daniel Micay wrote:
>>
>> So in your opinion, what's wrong with the `Boxes` section?
>>
>> http://static.rust-lang.org/doc/master/tutorial.html#boxes
>>
>> I happen to think it does a pretty good job of explaining why `~` is
>> required fo
+1
在 2013年11月19日 下午8:27，"Gaetan" 写道：
> "The most common use case for owned boxes is creating recursive data
> structures like a binary search tree."
>
> I don't think this is the most common use of owned boxes: string
> management, ...
>
> I don't think it a good idea to place "binary search tree"
> Owned boxes shouldn't be commonly used. There's close to no reason to use
one for anything but a recursive data structure or in rare cases for an
owned trait object.
>
> http://static.rust-lang.org/doc/master/tutorial.html#boxes
>
> It's important to note that ~[T] and ~str are not owned boxes. T
50 matches
Mail list logo
