Tomi,
Once the new discourse instance is set up it will be publicized on the home
page, and we may also decide then to put the internals forum there as well,
since it's purpose will be less easily confused.
On Thu, Jan 22, 2015 at 10:33 PM, Tomi Pieviläinen tomi.pievilai...@iki.fi
wrote:
My
You likely have already noticed, but traffic to rust-dev has decreased
dramatically in recent months. This was a result of natural changes in
project coordination at first, and then an intentional effort to phase out
the list.
In the beginning of the project there were only two places to talk
I believe it is not possible to link to glibc statically. My
understanding is that to get a Rust binary that does not depend on a
system-provided libc at all we need to add explicit support for
alternate libc implementations[1].
[1]: https://github.com/rust-lang/rust/issues/7283
On
Brian Anderson bander...@mozilla.com
Brian Campbell lam...@continuation.org
Brian Koropoff bkorop...@gmail.com
Cameron Zwarich zwar...@mozilla.com
Carol Nichols carol.nich...@gmail.com
Chris Morgan m...@chrismorgan.info
Chris Nixon chris.ni...@sigma.me.uk
Christoph Burgdorf christoph.burgd...@bvsn.org
Thanks for the updates, Tony.
On 09/29/2014 10:39 PM, Tony Arcieri wrote:
I've been trying to keep an eye on what's been brewing in the Rust
crypto-world. There's a lot of parts that people have been working on
that I'd really love to see brought together in a coherent manner,
perhaps in the
AM, John McKown john.archie.mck...@gmail.com wrote:
On Thu, Sep 4, 2014 at 8:59 PM, Brian Anderson bander...@mozilla.com wrote:
Thanks for the report. It's probably
https://github.com/rust-lang/rust/issues/13728. This is an easy first bug to
fix if somebody wants to jump on it.
Thanks
Thanks for the report. It's probably
https://github.com/rust-lang/rust/issues/13728. This is an easy first
bug to fix if somebody wants to jump on it.
On 09/04/2014 06:57 PM, John McKown wrote:
I run as a normal user (non-root) on Linux using Fedora 20 x86_64. I
did a git clone of rust just
Right now the options are to use the default in-tree build, or your own
out-of-tree build. The out-of-tree build is risky because it doesn't
carry our patches and isn't tested.
You are suggesting that we also provide official LLVM snapshots. This
has been considered many times but never done
I will ship stickers to anybody doing promotion for Rust. Email me your
shipping address and the quantity in private.
On 08/27/2014 02:31 PM, Paul Nathan wrote:
Hi,
Sept 8 is the next meet up time for Rust in Seattle. While I could get
my fine employer to host again, I think another venue
Awesome, Glenn! Thanks. Racer all the things.
On 08/25/2014 02:54 PM, Glenn Watson wrote:
Hi,
I've started a simple integration of the RACER code completion utility
for Sublime Text 3.
Source code (and more information) is available here:
https://github.com/glennw/RustAutoComplete
You can
If I want to hack on zinc, what do I need? Should I bring some type of
hardware? I have no experience with Arduino, etc.
On 08/13/2014 08:39 PM, Alan Andrade wrote:
Hi Rusties,
The first SF hack night is happening next Tuesday
http://www.meetup.com/SF-Rust-Hacknights/events/194585552/ and we
Added to the calendar:
https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.comctz=America/Los_Angeles
On 08/07/2014 08:59 AM, Tetsuharu OHZEKI wrote:
Hello Rust Ninjas!
I announce the Rust Meetup in Tokyo on Sunday September 27th, 2014,
at Mozilla
Here's the current state of official project support for various forums:
* discourse.rust-lang.org is for *discussion of the development of Rust
itself*. It is maintained by Mozilla.
* r/rust is for user discussion. It is maintained by the community.
* rust-dev is for user discussion. It is
Thanks, Simon!
This is huge. Simon knows everything about web standards, and this is
Servo's URL type, so it's going to be maintained and correct.
The old url crate was originally written by me, without looking at any
specs, in order to teach Servo able to open `http://www.google.com`. It
I'm really looking forward to this!
On 07/24/2014 02:18 AM, Ilya Dmitrichenko wrote:
Hi Simon,
I and @farcaller where thinking to prepare a talk on Zinc project
(http://zinc.rs/).
What length of the talks you guys do?
Cheers,
___
Rust-dev mailing
Doing this is a goal, but we're going to need a complete strategy -
let's please not start doing this too hastily. Maintaining crates out of
tree is not easy, and we need to have the systems in place that will let
us succeed (particularly around integration). acrichto will need to be
involved
I expect moving crates out of the main tree to be important for reducing
build cycle time.
On 07/21/2014 02:28 PM, Ilya Dmitrichenko wrote:
It would be great to discuss which libraries can be removed from the
main tree, I can see that there had been some progress with liburl
[1], but there
As to your original question about candidate libs, here are mine:
arena
fourcc
glob
graphviz (with some rustc refactoring)
hexfloat
regex
url
uuid
On 07/21/2014 02:28 PM, Ilya Dmitrichenko wrote:
It would be great to discuss which libraries can be removed from the
main tree, I can see that
On 07/18/2014 03:43 PM, Aljaž Srebrnič wrote:
On 17/lug/2014, at 20:08, Brian Anderson bander...@mozilla.com wrote:
Thanks for your work on MacPorts. Did you use any flags to configure or
arguments to make? What version of OS X, clang/gcc?
Yes, sorry, I’m building this on OS X 10.9.4
Thanks for your work on MacPorts. Did you use any flags to configure or
arguments to make? What version of OS X, clang/gcc?
On 07/17/2014 01:17 AM, Aljaž Srebrnič wrote:
Hello list,
I’m ono of the maintainers of rust on MacPorts, and I found some issues with
the build. The script in
On 07/11/2014 12:09 PM, Zoltán Tóth wrote:
On Wed, Jul 9, 2014 at 12:57 AM, Brian Anderson bander...@mozilla.com
mailto:bander...@mozilla.com wrote:
# Impact
Installing rustc to non-default locations will result in an
installation that puts some important libraries
On 07/13/2014 12:10 AM, Christoph Husse wrote:
Hi,
I successfully managed to hook into the compiler so far. Or well it's
not that successful, because it doesn't work, but at least the code is
there ;).
Now I am trying to compile an empty file, and it gives me the weird error:
error: can't
Can somebody file an issue described exactly what we should do and cc me?
On 07/14/2014 01:13 AM, richo wrote:
On 10/07/14 17:15 +, Ivan Kozik wrote:
On Thu, Jul 10, 2014 at 3:49 PM, Jonas Wielicki
j.wieli...@sotecware.net wrote:
While this is a good thing /all/ software projects should
Thanks, Aaron. This is going to be an important reference for authors. I
love the sensible organization and that it's already seeded with many of
our existing conventions.
On 07/11/2014 11:49 AM, Aaron Turon wrote:
Rustafarians,
As we head toward 1.0, we need to do do more than stabilize the
Reason: image not found
Trace/BPT trap
On 9 July 2014 00:53, Brian Anderson bander...@mozilla.com
javascript:; wrote:
Yes, it does.
On 07/08/2014 04:41 PM, Simon Sapin wrote:
On 08/07/14 23:57, Brian Anderson wrote:
*Running rustc directly
Hi.
Very soon now the way rustc links crates dynamically is going to
change[1], and it will impact the way you work with Rust in some
important cases. The TL;DR is that rustc will no longer encode RPATH
information in the binaries it produces, so the dynamic linker will be
less likely to
Yes, it does.
On 07/08/2014 04:41 PM, Simon Sapin wrote:
On 08/07/14 23:57, Brian Anderson wrote:
*Running rustc directly from the build directory will no longer work by
default*. To do this either set LD_LIBRARY_PATH or pass --enable-rpath
to the configure script.
Does this also apply
On 07/02/2014 11:19 AM, Gábor Lehel wrote:
Thanks, this is a good step, as is delaying taking actions by a day as
proposed in the meeting itself.
If you have any suggestions for how this regular email or the
process in general could be improved, please let us know.
Most
It does seem like rustdoc could be extended to do something
approximating literate programming without much hassle. I'd like to see
this project built out-of-tree using the rustdoc and rustc API's.
On 06/29/2014 12:38 PM, Evan G wrote:
I'm not sure if this is exactly what you're looking for,
This is very well presented for an alpha. Nicely done. So excited to see
projects start using it.
On 06/23/2014 10:50 PM, Yehuda Katz wrote:
Folks,
I'm happy to announce that Cargo is now ready to try out!
The Cargo repository is now at https://github.com/rust-lang/cargo and
you can learn
This weekend I'll be moving the Rust buildbot master and bors over to a
new machine. There will be some downtime but otherwise no new changes.
That is all.
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
Thanks, Hans! Rust CI is a fantastic resource and I'm glad it's running
smoothly again.
On 06/18/2014 01:11 AM, Hans Jørgen Hoel wrote:
Hi,
Rust Ci wasn't working for a period due to problems with building the
nightly PPA for the platform used by Travis (required GCC version was
bumped with
Thanks, Felix. I agree with your interpretation, and hope this gives
some clarity on why decisions are being made as they are.
That so many RFC's don't make it through the process is disappointing I
imagine, but is a reality of where we are in Rust's lifecycle. At this
point the fundamental
Hi, folks.
I've just moved the main repo from the 'mozilla' organization to
'rust-lang': https://github.com/rust-lang/rust. This has been a while
coming and reflects that Rust is a major project with its own community
and culture, and not simply another project under the Mozilla umbrella.
Thanks, Steve! This is going to do wonders for our fit and finish going
into the home stretch for 1.0.
On 06/16/2014 03:10 PM, Steve Klabnik wrote:
Hey all! I wrote up a blog post that you all should know about:
http://words.steveklabnik.com/rusts-documentation-is-about-to-drastically-improve
This is an interesting idea, but I don't see it happening for a long
time if ever:
* The current process is working fine
* rustc depends on many of the standard libraries, so restricting rustc
means figuring out how to stick to a fixed subset of those libraries
* It's a lot of work to make
Thanks!
On 06/08/2014 01:10 AM, Dietrich Epp wrote:
Unless there’s a good objection I’m taking ownership of the datetime library,
as luisbg’s efforts seem to be abandoned. I’ve read the wiki, the last mailing
list discussion, and I’ve familiarized myself with JSR 310, Joda Time, Noda
Time,
Again, I must ask you to stop. Claiming that we are 'ignoring the
developments of research' is *extremely* insulting.
I've turned moderation on for your account. Further messages to this
mailing list will need to be approved by the admins.
On 06/05/2014 11:00 PM, Suminda Dharmasena wrote:
I appreciate your enthusiasm, but please stop creating new threads that
simply suggest adding major new features to the type system. The vast
majority of type system features that might benefit Rust have been
discussed many times, in excruciating depth, for years.
On 06/05/2014 02:14 AM,
Greetings, all.
Looking for ways to have an impact on Rust? The current plan for Rust
defers the creation of some key libraries until after Rust 1.0, but that
doesn't mean we can't start on them now if the interest is out there.
Here are 7 libraries that need to be created soon rather than
Thank you for your suggestion, but typestate is not coming back. There
is no room in the complexity budget for another major piece of type
system, and linear types can serve much the same purpose.
On 06/04/2014 10:11 PM, Suminda Dharmasena wrote:
Hi,
The initial Type State implementation in
On 05/15/2014 09:30 PM, Tommi wrote:
On 2014-05-16, at 7:14, Daniel Micay danielmi...@gmail.com wrote:
On 16/05/14 12:10 AM, Tommi wrote:
I was just wondering, why do we have to explicitly specify the lifetimes of
references returned from functions? Couldn't the compiler figure those
The exact versions of the tooling here is pretty important - our ability
to support debugging is extremely version dependent, especially when it
comes to lldb.
On mac I believe we are not putting any particular effort into
supporting gdb at this point since lldb is the future. Newer lldb's
This is amazing!
I added it to the wiki https://github.com/mozilla/rust/wiki/Doc-examples
On 04/25/2014 07:25 PM, Jorge Aparicio wrote:
Hello fellow Rusticans,
I'm pleased to announce the Rust by example website [1], which is a Rust
version of the Go by example website [2], aimed at
I'm not sure what you are asking for here. Have you submitted this as a
pull request to http://github.com/rust-lang/rfcs?
I do realize that the RFC process takes time to get things approved, but
some have been, and I expect the rate of approvals to continue steadily.
On 04/17/2014 08:27 PM,
This sounds very useful. Thanks for letting us know.
On 04/22/2014 09:10 AM, Vladimir Pouzanov wrote:
This is the project I've been tinkering with for a good number of
weekends — zinc, the bare metal stack for rust is available at
https://github.com/hackndev/zinc.
I've just finished a major
Hey there, Rusticators,
Grand news! Starting today Aaron Turon is joining the Rust team. Aaron
did his PhD thesis on concurrency at Northeastern University, where he
published widely-noted papers on 'reagents' and 'LVars'. He will be
focusing on making Rust's standard libraries the best they
Hi.
I've been convinced recently that Rust is missing crucial documentation
of a particular nature: using Rust in practice. I would like to have
such a standalone guide, and these are some ideas about what should be
in it.
This is a guide that runs through creating an entire Rust project
On 04/17/2014 12:21 AM, Flaper87 wrote:
2014-04-17 2:11 GMT+02:00 Alex Crichton a...@crichton.co
mailto:a...@crichton.co:
The template which breaking changes will be required to look like is:
First, a brief one-line summary of the change
Second, take as long as is
On 04/17/2014 07:39 AM, Tommi wrote:
Can someone explain me why the module system maps to the file system in the way
it does? The problem is that you can end up with these modules named mod.rs
instead of the more informative names. If you have the following modules:
foo
foo::lut
bar
bar::lut
On 04/15/2014 10:12 AM, Patrick Walton wrote:
Hi everyone,
I'd like to remove the `~foo` literal syntax for owned strings in both
expressions and patterns. After dynamically sized types, this syntax is
the last remnant of the strange parser behavior by which the parser does
something different
It turns out this was premature and the bots are still using the old
toolchain. I'll keep working on it.
On 04/10/2014 05:05 PM, Brian Anderson wrote:
After a long time coming, the Rust windows bots are now running an
up-to-date mingw-w64 toolchain. This was a very easy transition thanks
I have a new bot up now that is *definitely* using the new toolchain.
Haven't completed a build yet, but I think it's going to work.
On 04/11/2014 04:16 PM, Thad Guidry wrote:
LOL. OK, and I'll keep me fingers crossed. ;)
On Fri, Apr 11, 2014 at 3:40 PM, Brian Anderson bander...@mozilla.com
Thank you for your interest, but this is not a constructive topic for
this venue.
On 04/10/2014 11:35 AM, Jason Long wrote:
Hello Folks.
How are you?
I want to know something about Rust language and Is it C killer? I mean
is that in the future is it a replacement for C?
Cheers.
Sorry for the curt response. The answer is that Rust is suitable for
many of the same tasks as C. Thank you.
Please do not have this discussion here.
On 04/10/2014 11:58 AM, Brian Anderson wrote:
Thank you for your interest, but this is not a constructive topic for
this venue.
On 04/10/2014
After a long time coming, the Rust windows bots are now running an
up-to-date mingw-w64 toolchain. This was a very easy transition thanks
to the efforts of our windows devs, including Vadim, Thad, and klutzy.
The practical impact of this is that windows developers should prefer
the mingw-w64
I've been worried about this decision too.
On 04/02/2014 10:34 AM, Steve Klabnik wrote:
I compiled from source just yesterday, but everything's been going swimmingly!
I just have one comment on 0.10: It seems like println was removed
from the prelude. While I can totally appreciate that most
On 03/28/2014 05:13 AM, Ben Noordhuis wrote:
On Fri, Mar 28, 2014 at 2:25 AM, Brian Anderson bander...@mozilla.com wrote:
Hi.
I have very exciting news. Rust now has binary installers for Linux and Mac,
as well as nightly builds for Windows, Linux and Mac.
Official Rust installers now come
Not in the near term I think, at least as long as it's I that has to do
the automation - there are many other automation changes already in the
pipeline just for linux/mac/win.
I am at this point amenable to opening up our infrastructure to one or
two trusted and motivated individuals, since
.
--
Ian
On Fri, Mar 28, 2014 at 4:52 PM, Brian Anderson bander...@mozilla.com
mailto:bander...@mozilla.com wrote:
Not in the near term I think, at least as long as it's I that has to
do the automation - there are many other automation changes already
in the pipeline just for linux/mac
, Brian Anderson wrote:
I don't actually know what the issue is with Rust on
arm-linux-unknown-gnueabihf. Is cross-compiling to this architecture
with Rust difficult? Why do we need binaries?
One thing we could possibly do without much difficulty is let external
build slaves connect to our build
I appreciate your concern, but I don't think a moratoreum is necessary;
memory safety is parament to Rust, so the idea of adding 'unsafe
features to the safe subset of Rust' is an oxymoron.
On 03/28/2014 08:12 PM, Tony Arcieri wrote:
I really love the semantics of the safe subset of Rust.
It looks like I can set the digest size threshold very large and then
force it to be sent every day when it never hits that threshold. I'll
try. Let me know if anything breaks.
On 03/28/2014 09:43 AM, Steven Stewart-Gallus wrote:
The recent giant discussion over unsafe bounds checking
Good luck at the meetup tonight, Tom. The last one I attended in PDX was
a lot of fun.
On 03/26/2014 12:01 PM, Tom Lee wrote:
Hey folks,
Per the subject, there's a Rust meetup in Portland, OR tomorrow night
from 6:30pm. Details here:
http://calagator.org/events/1250465822
I'm waiting on a
Hi.
I have very exciting news. Rust now has binary installers for Linux and
Mac, as well as nightly builds for Windows, Linux and Mac.
Official Rust installers now come in the following forms:
* source .tar.gz - the same old source tarball
* binary .tar.gz - Generic Unix installers,
That's right. I didn't mention it because nothing has changed (yet) in
the windows installers. Sorry for the confusion.
On 03/27/2014 06:59 PM, Matthew McPherrin wrote:
On Thu, Mar 27, 2014 at 6:25 PM, Brian Anderson bander...@mozilla.com wrote:
I have very exciting news. Rust now has binary
On 03/27/2014 09:05 PM, György Andrasek wrote:
curl -s http://www.rust-lang.org/rustup.sh | sudo sh
Can we please not recommend people pipe random text from across the
internet into a fricking *root shell*?
Yes. In fact my original email said exactly that.
:
On Sat, Mar 22, 2014 at 12:55 AM, Brian Anderson bander...@mozilla.com wrote:
I'm in the process of rewriting most of the installation code and I'm at the
point where it's almost done, and I'm looking at the options to configure
that affect installation destinations and wondering which really must
I'm in the process of rewriting most of the installation code and I'm at
the point where it's almost done, and I'm looking at the options to
configure that affect installation destinations and wondering which
really must be implemented.
configure supports a variety of standard options that
This appears to be all the doc-sprint-inspired PR's. More than I expected!
https://github.com/mozilla/rust/pull/12982
https://github.com/mozilla/rust/pull/12968
https://github.com/mozilla/rust/pull/12954
https://github.com/mozilla/rust/pull/12955
https://github.com/mozilla/rust/pull/12956
Dearest Rustlers,
Today I'm super-excited to announce that Mozilla has arranged to develop
a world-class package manager for Rust. Yehuda Katz and Carl Lerche,
from Tilde Inc., have previously built the popular Ruby package manager,
Bundler, and now they are going to build Rust's package
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 long time and I know very few
others that were using it. If it does impact you, I'm sorry for the
, Brian Anderson bander...@mozilla.com
mailto:bander...@mozilla.com wrote:
This weekend Mozilla's Mountain View office is moving, and along
with it some of Rust's build infrastructure. There will be downtime.
Starting tonight bors is not gated on the mac or android builders
On 03/12/2014 12:54 AM, Flaper87 wrote:
2014-03-12 2:11 GMT+01:00 Brian Anderson bander...@mozilla.com
mailto:bander...@mozilla.com:
[snip]
-
Many changes, including bug fixes and documentation improvements can
be implemented and reviewed via the normal GitHub pull request
On 03/12/2014 03:42 AM, Simon Sapin wrote:
On 12/03/2014 01:11, Brian Anderson wrote:
* Fork the RFC repohttp://github.com/rust-lang/rfcs
* Copy `-template.md` to `active/-my-feature.md` (where
'my-feature' is descriptive. don't assign an RFC number yet).
* Fill in the RFC
* Submit
This weekend Mozilla's Mountain View office is moving, and along with it
some of Rust's build infrastructure. There will be downtime.
Starting tonight bors is not gated on the mac or android builders and
those machines are turned off. Sometime this weekend other build
machines, including the
The downsides you list are all more or less applicable to this design,
indeed. We are seeing real requirements in real code that indicates that
the current abstraction facilities provided by Rust are efficient enough
for certain demanding use cases (the DOM in particular).
Here are the
Hey, Rusties.
The freewheeling way that we add new features to Rust has been good for
early development, but for Rust to become a mature platform we need to
develop some more self-discipline when it comes to changing the system.
So this is a proposed modification to our current RFC process to
Hey,
As you may know, we've got our first doc sprint scheduled for Sunday,
12-4 Pacific time. We'll to set up the commons area at the SF office
with pizza and turn on video conferencing for remoties. Before that day
comes though we need to come up with some kind of plan, something that
is
Hi.
Last week a number of us got together to hash out designs for the
remaining features in Rust 1.0, with the goal of producing RFC's for
each in the upcoming weeks.
I'm very optimistic about how it's all going to come together, and that
the quantity of work to be completed is reasonable.
There is not.
I am interested in this topic. There is a great deal of public
information about Rust's development and I'd love it to be organized in
an accessible way. With the right presentation it could be interesting,
dramatic, and maybe even useful to other designers.
On 02/28/2014
On 02/24/2014 10:15 PM, Erick Tryzelaar wrote:
Brian: yes, at the moment `#[deriving(Hash)]` does support more than
SipHash. However this PR temporarily removes that feature to replace
`#[allow(default_type_param_usage)]` with `#[feature(default_type_params)]`:
Thanks, Erick! This was an awesome effort that greatly improves the
ergonomics of hashing.
On 02/24/2014 08:31 AM, Erick Tryzelaar wrote:
I'm happy to announce that Rust's new hashing framework has landed in:
https://github.com/mozilla/rust/pull/11863
On 02/19/2014 02:37 AM, György Andrasek wrote:
On Wed, Feb 19, 2014 at 1:40 AM, Brian Anderson bander...@mozilla.com wrote:
Backwards-compatibility is guaranteed.
Does that include ABI compatibility?
Second, the AST is traversed and stability index is propagated downward to any
indexable
Hey there.
I'd like to start the long process of stabilizing the libraries, and
this is the opening salvo. This process and the tooling to support it
has been percolating on the issue tracker for a while, but this is a
summary of how I expect it to work. Assuming everybody feels good about
This may be the most canonical description of target triples (autoconf
config names): https://sourceware.org/autobook/autobook/autobook_17.html
Triples are just a short way of identifying a compilation target, and
their naming is mostly out of our hands, established by historical
precedent.
On 02/11/2014 01:01 AM, Tom Lee wrote:
Hey Brian,
Not sure I understand the last paragraph of your email (do you or do
you not want to encourage distro-specific installation? :))
I'm still not sure. I want people to be able to install Rust easily and
I want those sources to be reliable.
On 02/01/2014 02:59 PM, Benjamin Striegel wrote:
Yes, and I don't have a solution for that.
Well, it's not like we don't already stumble here a bit, what with
requiring :: instead of just . Not sure how much other people
value the consistency here.
Yeah, the existing solution is bad, and
I'm convinced by this thread that this issue should be put to bed
forever. I added a note to the design faq issue:
https://github.com/mozilla/rust/issues/4047#issuecomment-33751021
On 01/30/2014 03:20 PM, Benjamin Striegel wrote:
https://github.com/mozilla/rust/issues/2643
I came here to
On 01/29/2014 06:35 PM, Patrick Walton wrote:
On 1/29/14 6:34 PM, Samuel Williams wrote:
Perhaps this has been considered already, but when I'm reading rust code
let mut just seems to stick out all over the place. Why not add a
var keyword that does the same thing? I think there are lots of
Hey Rustlers.
I've just instructed our friendly bot, bors, to start rejecting pull
requests that don't pass the test suite on Android. This has been a long
time coming, but from now on our Android support should be much more
consistent. This will make it incrementally harder to land certain
Hey again, Rusticians.
So I think most of us know that rustpkg isn't quite working the way
people expect, and the general consensus seems to be that its flaws
extend pretty deep, to the point where it may just not be exposing the
right model. I'd like to deprecate it immediately to end the
People interested in Rust are often looking for ways to have a greater
impact on its development, and while the issue tracker lists lots of
stuff that one *could* work on, it's not always clear what one *should*
work on. There is consistently an overwhelming number of very important
tasks to
On 01/25/2014 08:58 AM, Bill Myers wrote:
Stack management for green tasks has been based in the past first on segmented
stacks and then on standard large stacks.
However, I just realized that there is a third alternative which might well be
better than both of those.
The idea is very
On 01/13/2014 10:15 PM, Liigo Zhuang wrote:
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().
Agree, though I haven't heard any great suggestions yet. The core
problem is
I've opened an issue on the naming problem
https://github.com/mozilla/rust/issues/11765
On 01/23/2014 08:55 PM, Benjamin Striegel wrote:
If we're going to quibble over names we might as well call the types
Sender and Receiver.
Really though, EVERYONE is fine with the proposed semantics from
Tell me how many you need (if you want a lot then maybe mention why) and
a shipping address.
On 01/14/2014 05:30 PM, Brian Anderson wrote:
People that need Rust stickers can send me an email off-list.
On 01/14/2014 03:45 PM, Christopher Meiklejohn wrote:
Who do we contact if we're running
This sounds very promising. Like Gaetan, I believe that a central
package database is a critical piece of infrastructure for the Rust
community. I haven't made any effort in this direction yet because our
packaging tool isn't ready, but I fully encourage people to work on
this. The rust issue
This is awesome, and with some refinement this may be what we want to
make the official introductory documentation. I left some feedback on HN.
On 01/13/2014 09:08 AM, Steve Klabnik wrote:
Also posted to my blog:
http://words.steveklabnik.com/a-30-minute-introduction-to-rust
I've just kept
After seeing the title of this email I hoped that it was me. Regardless
there's no need to blame anyone. Somebody was nice enough to go through
and add docs and put in a FIXME. All part of the process.
On 01/13/2014 05:25 PM, Andrew Pennebaker wrote:
Who wrote these 0.8 docs:
1 - 100 of 432 matches
Mail list logo
