Hi Nadav,
This list is defunct. You should use users.rust-lang.org. See
https://www.rust-lang.org/community
for other places to communicate.
On Fri, Apr 26, 2019, at 07:03, Nadav Vinik wrote:
> Hello
>
> I don't know why you don't want to implement heritage of classes but it
> will be easier
Note that it *is* linked, through
https://github.com/rust-lang/rust/wiki/Note-guide-for-new-contributors,
just not the homepage.
On Fri, Jan 23, 2015 at 10:59 AM, Steve Klabnik st...@steveklabnik.com
wrote:
The current discourse has not been linked because it's for compiler
internals and
You need at least a 32-bit stdlib, but you can build with `cargo build
--target i686-unknown-linux-gnu` and it will Just Work assuming you have
the proper libs in $PREFIX/lib/rustlib/i686-unknown-linux-gnu.
http://doc.rust-lang.org/src/rustc_back/target/mod.rs.html#330 has a list
of the built-in
the contents of the json file
that is passed.
Corey Richardson can help you with that.
--
Valerii
--
http://octayn.net/
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
The target specs that rustc will use won't be relevant to the build
system. Adding things to platform.mk is how the build system is
extended, right now, and I don't foresee that changing.
On Fri, Oct 17, 2014 at 5:19 PM, Cody P Schafer d...@codyps.com wrote:
On Fri, Oct 17, 2014 at 4:41 PM, Ben
LLVM already has support for instrumenting code to generate gcov data,
I believe Luqman and Huon have looked into this, at least slightly.
On Wed, Oct 8, 2014 at 9:09 PM, Sean McArthur smcart...@mozilla.com wrote:
A project I'd love to see (either separate, or eventually baked into the
test
https://github.com/PistonDevelopers/rust-image
On Mon, Sep 8, 2014 at 9:44 AM, Oldřich Vetešník
oldrich.vetes...@gmail.com wrote:
Hello,
I’m curious - is there a PNG processing lib for Rust? I’d like to write a
tiny client tool for processing a directory of images into HTML and I’ll need
See http://www.cs.indiana.edu/~eholk/papers/hips2013.pdf and
http://blog.theincredibleholk.org/blog/2012/12/05/compiling-rust-for-gpus/
for prior work.
On Sat, Sep 6, 2014 at 1:09 PM, Madhu Srinivasan
smadhuea...@outlook.com wrote:
Hello fellow Rustians,
I am wondering (before attempting
Patch here: https://github.com/rust-lang/rust/pull/16156
If you cross compile, or can test on perhaps-lesser-used setups, I
would very much appreciate a `make check`. This is touching all the
fiddly bits of linking, so it's not very easy to test.
Thanks!
--
http://octayn.net/
Atom feed is in the same place it always has been:
http://blog.octayn.net/atom.xml and
On Mon, Jul 28, 2014 at 1:20 AM, Diggory Hardy diggory.ha...@unibas.ch wrote:
Any chance you can add RSS feeds on the new blog?
On Sunday 27 Jul 2014 11:52:52 Corey Richardson wrote:
Been super busy
Been super busy, but there's some good stuff in store:
http://blog.octayn.net/blog/2014/06/09/future-of-twir/
On Sun, Jul 27, 2014 at 9:46 AM, Nathan Typanski ntypan...@gmail.com wrote:
It's moved here http://blog.octayn.net/, although there hasn't been
an update since 15 July.
Nathan
Not right now. Extending the language to allow this is the subject of
RFC 24: https://github.com/rust-lang/rfcs/blob/master/active/0024-traits.md
On Tue, Jul 22, 2014 at 9:50 AM, Allen Welkie allen.wel...@gmail.com wrote:
Can there be two simultaneous implementations of a generic trait? I ask
You can avoid monomorphization by using trait objects, which erase
the precise implementing type through a vtable + pointer.
http://doc.rust-lang.org/tutorial.html#trait-objects-and-dynamic-method-dispatch
has some documentation.
On Tue, Jul 22, 2014 at 10:16 AM, Lionel Parreaux
I believe it has long been the goal that once we have a robust package
manager, we would start moving everything we could get away with out
of the tree. Cargo is pretty awesome now, and I think we could get
away with moving those out, with the caveat that cargo depends on
semver..
On Mon, Jul 21,
That's right. `BufferedReader` takes the `Reader` it wraps by-value,
but the `read` method takes `mut self`. Moving something doesn't
require it to be stored in a mutable variable, but taking a `mut` to
it does.
On Sun, Jul 20, 2014 at 6:29 PM, David Henningsson di...@ubuntu.com wrote:
Hi,
Complaining about something I don't like:
Due to the choice of MPLv2, this won't be usable in the wider Rust
ecosystem, which is MIT/ASL2 focused. In particular, section 3.2(a)
requires that any distribution in Executable Form carry a notice
about how to acquire the source code of zmq.rs. This is
:
On 07/02/2014 03:16 AM, Corey Richardson wrote:
Complaining about something I don't like:
Due to the choice of MPLv2, this won't be usable in the wider Rust
ecosystem, which is MIT/ASL2 focused. In particular, section 3.2(a)
requires that any distribution in Executable Form carry a notice
The full syntax is: box [( EXPR )] EXPR
The first expression is the boxer, or where the result of the second
expression will be stored. GC and HEAP are special cased right now as
the only boxers, but the goal is to use a trait such that you can use
Rc, arenas, vectors, or any other arbitrary type
There is an Ubuntu PPA available at
https://launchpad.net/~cmrx64/+archive/cargo, for use on travis or
otherwise.
On Mon, Jun 23, 2014 at 10:50 PM, Yehuda Katz wyc...@gmail.com wrote:
Folks,
I'm happy to announce that Cargo is now ready to try out!
The Cargo repository is now at
Hey Jussi,
Very cool! Always happy to see tools with Rust support :) As to file
names, do you know about `rustc --crate-file-name`?
On Wed, Jun 18, 2014 at 3:17 PM, Jussi Pakkanen jpakk...@gmail.com wrote:
Hi
I'm working on a build system called Meson
(https://jpakkane.github.io/meson/) and
Or bound by Copy.
On Thu, Jun 12, 2014 at 10:17 AM, Patrick Walton pwal...@mozilla.com wrote:
You could just clone the value to get around that error.
On June 12, 2014 10:03:40 AM PDT, Tommi rusty.ga...@icloud.com wrote:
On 2014-06-12, at 19:08, Patrick Walton pcwal...@mozilla.com wrote:
It's called Copy. `trait Foo: Copy { ... }`.
On Thu, Jun 12, 2014 at 10:26 AM, Tommi rusty.ga...@icloud.com wrote:
I think a new keyword, something like `stable`, is needed for specifying that
an argument passed to a trait function is guaranteed to be logically
unchanged after the function
to a discussion about adding to Rust the
C++ like optimization of moving rvalues (of non-Copy types) when they're
passed to certain functions.
On 2014-06-12, at 20:30, Corey Richardson co...@octayn.net wrote:
It's called Copy. `trait Foo: Copy { ... }`.
On Thu, Jun 12, 2014 at 10:26 AM, Tommi
We have a ragel backend. https://github.com/erickt/ragel
On Thu, Jun 12, 2014 at 3:28 PM, richo ri...@psych0tik.net wrote:
On 11/06/14 15:43 +0900, Akira Hayakawa wrote:
Hi,
Haskell's Parsec is really a good tool to parse languages.
Scala also has the equivalent.
What about Rust?
Keeping in mind that the `self` value here can be a reference. Ie,
implementing the traits also for references to a type.
On Wed, Jun 11, 2014 at 11:47 AM, Tommi rusty.ga...@icloud.com wrote:
On 2014-06-11, at 21:33, Daniel Micay danielmi...@gmail.com wrote:
Cloning big integers, rationals
I currently have 4246 builds of rustc, going back to a little bit
before bors started being used.
On Mon, Jun 9, 2014 at 10:16 AM, Steve Klabnik st...@steveklabnik.com wrote:
I have this pipe dream of compiling every Rust version ever and GPG
signing them though heh.
You need to change the target, not just the target-cpu. `rustc
--target arm-unknown-linux-gnueabihf ...`
On Sun, Jun 8, 2014 at 2:57 PM, Skirmantas Kligys
skirmantas.kli...@gmail.com wrote:
Luqman Aden laden@... writes:
Building a Rust cross compiler that can target arm isn't too hard. You
1.4GB peak, consumed by rustc and every child process. The bencher is
currently running after being down for a while, so it will fill in
today. There are no real workarounds.
On Thu, Jun 5, 2014 at 11:13 AM, Ian Daniher explodingm...@gmail.com wrote:
1GB is close-ish to the 1.4GB last reported
As with most things in Rust, in a pattern, a keyword means the
*opposite* of its normal meaning. So where `box e` in an expression
will box up the result of `e`, `box p` in a pattern will unbox `p`.
On Tue, May 27, 2014 at 9:50 AM, Tommi rusty.ga...@icloud.com wrote:
What is the meaning of this
Given the size of the binaries it looks like you may not have been
passing -O, which often gives the best code size.
On Thu, May 22, 2014 at 1:27 PM, Alexander Tsvyashchenko n...@endl.ch wrote:
Hi All,
Recently I was playing with bindings generator from C++ to Rust. I managed
to make things
No, there are no task-specific heaps. An old concept from the manual
is the exchange heap, which is where ~ boxes lived (ie, the normal
heap) and that @-boxes were some magic task-local heap. But you can
always send BoxT between tasks. There's been mention of wanting a
task-local box in IRC.
See https://github.com/mozilla/rust/wiki/The-Rusticon for an
up-to-date glossary and syntax reference.
On Tue, May 20, 2014 at 3:59 PM, Daniel Micay danielmi...@gmail.com wrote:
On 20/05/14 06:45 PM, Masanori Ogino wrote:
Hello.
I found that the Reference Manual uses the term owning pointer,
Sending it upstream is far better. Ping someone (probably Alex) to
upgrade our LLVM once it's merged.
On Tue, Apr 22, 2014 at 3:43 AM, Vladimir Pouzanov farcal...@gmail.com wrote:
The problem is that mrc is generated unless target is thumb1, but cortex-m3
is thumb2 that still doesn't support
`box foo` would create a SomeBox'static str, as outlined in the
meeting notes:
box foo - Heap'static Str
foo.to_owned() - HeapStr (or ~Str)
Heap::from(foo) - HeapStr (or ~Str)
Rc::from(foo) - RcStr
On Tue, Apr 15, 2014 at 2:06 PM, SiegeLord slab...@aim.com wrote:
On 04/15/2014 01:12 PM, Patrick
Hello all,
I now have on a disk here every merge into master that builds on my
machine, built. That is, 3733 copies, using 560GB of disk, of rustc
going back to the first run of bors on February 1, 2013. If there's
anything interesting you want to do with them, let me know!
--
-g, or --debuginfo (0|1|2) will generate debuginfo. -g means
--debuginfo 2. see rustc --help for more details.
On Thu, Apr 10, 2014 at 8:13 AM, Artella Coding
artella.cod...@googlemail.com wrote:
Previously I would have debugged using the command rustc -Z debug-info
example.rs. However with
range doesn't return a forward iterator. RangeA also implements
DoubleEndedIterator.
On Thu, Apr 10, 2014 at 12:53 AM, Kevin Ballard ke...@sb.org wrote:
On Apr 9, 2014, at 9:50 PM, Tommi Tissari rusty.ga...@icloud.com wrote:
On 10 Apr 2014, at 00:22, Kevin Ballard ke...@sb.org wrote:
FWIW,
You don't use bounds in the struct, you put them in the impl. So you
would instead say
struct LCDS {
spi: S,
...
}
and then:
implS: SPI LCDS {
...
}
On Tue, Apr 8, 2014 at 1:23 PM, Vladimir Pouzanov farcal...@gmail.com wrote:
I might have found an unsupported case.
Consider the
, Corey Richardson co...@octayn.net wrote:
You don't use bounds in the struct, you put them in the impl. So you
would instead say
struct LCDS {
spi: S,
...
}
and then:
implS: SPI LCDS {
...
}
On Tue, Apr 8, 2014 at 1:23 PM, Vladimir Pouzanov farcal...@gmail.com
wrote:
I
A C-style array is written `*T`, much like in C (note: I'm not saying
`T*` and `T[]` are the same type, I know they aren't)
On Sat, Apr 5, 2014 at 6:53 AM, Simon Sapin simon.sa...@exyr.org wrote:
On 05/04/2014 11:39, Vladimir Pouzanov wrote:
The problem is that [extern unsafe fn()] results in
Language suggestions should go through our new RFC process:
https://github.com/rust-lang/rfcs/blob/master/active/0001-rfc-process.md
On Thu, Apr 3, 2014 at 8:26 PM, Tommi rusty.ga...@icloud.com wrote:
I forgot to mention that this same space-optimization could be done for
Optionbool already.
On Wed, Apr 2, 2014 at 1:34 PM, Steve Klabnik st...@steveklabnik.com 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 people will
See our new RFC process for proposing changes to the language:
https://github.com/rust-lang/rfcs/blob/master/active/0001-rfc-process.md
On Mon, Mar 31, 2014 at 10:01 AM, Vladimir Pouzanov farcal...@gmail.com wrote:
I'd like to propose to extend the language with some concepts from nesC,
which
Alternatively, in this future where people are deploying Rust
applications to hundreds of thousands of servers, we could be using
Intel's Memory Protection Extensions for much cheaper bounds checking
etc. Which surely other applications will be using once bounds checks
are nearly free. Rust will
It's not about debugging, it's about memory safety. It'd be ridiculous
to disable bounds checking just because you've done QA. How many
security exploits are over- or under-flows?
On Thu, Mar 27, 2014 at 7:16 PM, Lee Braiden leebr...@gmail.com wrote:
I think the point is that the compiler should
Daniel Micay (strcat) already has a sandbox. It drives the rusti bot
in IRC, and has a web frontend sometimes available at
http://strcat.zapto.org:8000/. The source is at
https://github.com/thestinger/rust-playpen. There are plans to have a
VM run a similar thing on rust-lang.org
On Fri, Mar 28,
No. See https://github.com/mozilla/rust/pull/8955 and
https://github.com/mozilla/rust/issues/11871 for discussion. You can
stub out
morestack but that won't remove the stack size checks. It's sanest to
just compile the IR yourself (the stack checking is a target-specific
machine pass, which is why
Note that there's Rust support for Ragel
(https://github.com/erickt/ragel), so you can just use that. It's much
easier than writing out your state machines by hand.
On Sun, Mar 23, 2014 at 1:18 PM, Patrick Walton pcwal...@mozilla.com wrote:
On 3/23/14 9:04 AM, Clark Gaebel wrote:
I think the
No, due to the Rust Workweek that is this week.
On Thu, Mar 6, 2014 at 1:13 AM, Liigo Zhuang com.li...@gmail.com wrote:
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+
Notice that there was a link to a two-month old thread on the list.
His email is in that...
On Sun, Mar 2, 2014 at 11:44 PM, Fernando Pelliccioni
fpellicci...@gmail.com wrote:
I don't have the Steve's email address.
Please could someone provide it.
Thanks.
On Mon, Mar 3, 2014 at 1:41 AM,
Hello all,
I'm pleased to announce the 1.1.0 release of cargo-lite:
https://github.com/cmr/cargo-lite/tree/v1.1.0. You can install it
with `pip install cargo-lite`. See the readme for more details. A
summary:
cargo-lite is a very simple package manager, with no concept of
versioning. It requires
(My idea for the lint was `#[allow_kind(Name)]`
, which someone on IRC remarked as opt-out opt-in builtin traits
On Fri, Feb 28, 2014 at 4:36 PM, Gábor Lehel glaebho...@gmail.com wrote:
I think this is a really great idea.
There's another potential compromise that would preserve most of its
?
Is there something similar to #[deriving] ?
Thanks
Richard Gomes
http://rgomes.info
http://www.linkedin.com/in/rgomes
mobile: +44(77)9955-6813
inum: +883(5100)0800-9804
sip:rgo...@ippi.fr
On 27/02/14 00:21, Corey Richardson wrote:
We already have this. You just need to implement Hasher
This is problematic because name resolutions happens far after macro
expansion. I think this could be doable with an extremely limited
macro module system, but I think it's not-very-good to have the same
path syntax for two incredibly different systems.
On Tue, Feb 25, 2014 at 4:39 PM, Sean
Is this not already expressible with swap/replace? Is there a big
improvement here that I'm missing?
On Tue, Feb 25, 2014 at 4:23 PM, Kevin Ballard ke...@sb.org wrote:
I too was under the impression that you could not read from a
mutably-borrowed location.
I am looking forward to the ability
The size comes from statically linking to the standard library and
runtime. To keep size down, you can pass `-C prefer-dynamic` to rustc
to link to them dynamically instead.
On Mon, Feb 24, 2014 at 6:23 PM, S.A. qmt...@yahoo.com wrote:
Hello,
I am new to rust and have a question on what
You're assuming `use` loads code, but it only brings names into scope.
`mod submodule;` is what loads `submodule` into the crate. See
http://static.rust-lang.org/doc/master/tutorial.html#crates-and-the-module-system
On Wed, Feb 19, 2014 at 11:37 PM, benjamin adamson
adamson.benja...@gmail.com
Bors already mentions the pull request that he merged, and any commits
that close or work on issues usually mention that explicitly in their
commit message. What more do you want?
On Mon, Feb 17, 2014 at 6:40 PM, Nick Cameron n...@ncameron.org wrote:
This is a nice solution, I like it.
People
Hey all,
As you are probably aware, we use LLVM for code generation and
optimization. It is a large project, and one of its cooler features is
the variety of sanitizers it provides
(http://clang.llvm.org/docs/index.html#using-clang-as-a-compiler).
These are not clang-specific, but indeed can be
On Tue, Feb 4, 2014 at 12:23 PM, Daniel Micay danielmi...@gmail.com wrote:
On Tue, Feb 4, 2014 at 3:45 AM, Corey Richardson co...@octayn.net wrote:
Hey all,
As you are probably aware, we use LLVM for code generation and
optimization. It is a large project, and one of its cooler features
Also after sleeping on it I'm not as big of a fan of this proposal.
But, I find the idea raised earlier of having generic blocks to
group implementations etc that have the same implementation nice.
Fully backwards compat though, so I'm not going to worry about it.
Default typarams are awesome, but they're gated, and there's some
concern that they'll interact unpleasantly with extensions to the type
system (most specifically, I've seen concern raised around HKT, where
there is conflicting tension about whether to put the defaults at
the start or end of the
Hey all,
bjz and I have worked out a nice proposal[0] for a slight syntax
change, reproduced here. It is a breaking change to the syntax, but it
is one that I think brings many benefits.
Summary
===
Change the following syntax:
```
struct FooT, U { ... }
implT, U TraitT for FooT, U { ... }
On Sat, Feb 1, 2014 at 6:12 PM, Vladimir Lushnikov
vladi...@slate-project.org wrote:
Also, reusing 'for' would be confusing as well, because you expect a loop
there, not a generic type bound. How about 'any':
any is a super useful identifier and is already used. I do not want to
reserve it.
On Sat, Feb 1, 2014 at 6:24 PM, Eric Reed ecr...@cs.washington.edu wrote:
Responses inlined.
Hey all,
bjz and I have worked out a nice proposal[0] for a slight syntax
change, reproduced here. It is a breaking change to the syntax, but it
is one that I think brings many benefits.
Summary
On Sat, Feb 1, 2014 at 6:31 PM, Corey Richardson co...@octayn.net wrote:
On Sat, Feb 1, 2014 at 6:24 PM, Eric Reed ecr...@cs.washington.edu wrote:
Again, I strongly disagree here.
There IS only one function foo. Some of it's arguments are types. foo's
behavior *does not change* based
I see where Tony is coming from for this one. Just because we *can*
doesn't necessarily mean we should. If possible we should definitely
prefer to find a common version that both libraries can be happy with.
I myself don't have the answers to his questions, though.
On Fri, Jan 31, 2014 at 6:24
Last I did a survey, `let mut` was less than half (and more around
30-40%) of the `lets` I found, though it wasn't exhaustive. It's also
important to note that Rust is not a language suited for new
programmers. Far too many concerns; it tackles hard problems and makes
tradeoffs that new
You're not actually seeing a stack entry, you're seeing the string
that was given to `fail!()`. You can get a real backtrace with gdb,
break on `rust_fail`. You can also get a super crappy backtrace using
the backtrace function, see prototype
https://gist.github.com/cmr/8192817. We used to use it,
On Sat, Jan 18, 2014 at 10:30 PM, Scott Lawrence byt...@gmail.com wrote:
On Sat, 18 Jan 2014, Corey Richardson wrote:
Rust's safety model is not intended to prevent untrusted code from
doing evil things.
Doesn't it succesfully do that, though?
It might! But Graydon was very adamant
You realize you're using a 3 month old unsupported release of a
pre-alpha language, right? Anyway I don't know how those got promoted
to doc comments, they used to just be comments.
On Mon, Jan 13, 2014 at 8:25 PM, Andrew Pennebaker
andrew.penneba...@gmail.com wrote:
Who wrote these 0.8 docs:
I don't know what print_args is, but there's a getopt-alike in extra::getopts
On Sun, Jan 12, 2014 at 11:48 AM, Renato Lenzi rex...@gmail.com wrote:
If i want to access line command params i used code like this:
fn main() {
let args: ~[~str] = ::std::os::args();
println(args[0]);
}
Hi Abraham,
* Is there any built-in way to iterate over all values of a C-like enum?
It's not hard to define an iterator method that implements this for any
given type, but it's tedious boilerplate that seems better left to the
compiler.
Not really. What is your usecase? One
What type is `3`? There's know way to know. Use `3i` for int, `3u` for
uint, etc.
On Sat, Jan 11, 2014 at 12:17 PM, Renato Lenzi rex...@gmail.com wrote:
The code is trivial:
fn main()
{
let x = 3;
println(x.to_str());
}
the error is this (on Win7)
d:\Rust09\binrustc 00025.rs
This RFC isn't about using a single build system for everything, it's
the build system we use to build Rust itself.
On Fri, Jan 10, 2014 at 10:06 AM, Diggory Hardy li...@dhardy.name wrote:
A further point in favour of CMake is that it would make multi-language
projects easier to manage, in
On Fri, Jan 10, 2014 at 5:38 PM, Don Question
donquest...@rocketmail.com wrote:
Congrats to 0.9!
I'm coming from a C/C++/Python background and was loosely following the
progress of Rust
for quite a while now, but never tried it until yesterday.
I must admit i'm quite pleased so far, but i
The current consensus on this subject, afaik, is the rename int/uint
to intptr/uintptr. They're awful names, but it frees up int for a
*fast* bigint type. Fast here is key. We can't have a suboptimal
numeric type be the recommended default. We need to perform at least
as well as GMP for me to even
, Corey Richardson co...@octayn.net wrote:
We need to perform at least as well as GMP for me to even consider it.
The only realistic way to accomplish this is using GMP. Lots of other
big integer implementations exist with lots of work put into them and
the performance is not even in the same
Hey all,
The build system has grown a fair bit of complexity, and is getting
hard to understand. I've been thinking about what could replace it
moving forward. Most of the complexity stems from having to self-host
(ie, staging) and cross compilation (which target are we compiling
for, and with
Any such conversion is going to be lossy enough as to be worthless.
It's only acceptable for emscripten because the web platform can't run
native code. But any use of Rust is already going to be targetting
something that can run C.
On Sun, Jan 5, 2014 at 9:11 PM, Greg g...@kinostudios.com wrote:
Much of it would be. But why?
On Sun, Jan 5, 2014 at 9:25 PM, Huon Wilson dbau...@gmail.com wrote:
On first glance it seems like C - Rust would be very feasible via a lot of
`unsafe`, * and *mut.
On 06/01/14 13:21, Corey Richardson wrote:
Any such conversion is going to be lossy enough
oslo.config looks decent. On some projects I've worked on, we started
out using INI files but found them severely lacking once we wanted to
extend the options. We ended up using libconfig[0], which I think is
an excellent library. In multibuilder[1], we use extra::serialize to
load a config
If you slap a #[no_uv]; on the benchmark, it will use libnative, which
is threads
On Sat, Jan 4, 2014 at 11:16 AM, Michael Neumann mneum...@ntecs.de wrote:
Am 04.01.2014 17:14, schrieb Michael Neumann:
Hi all,
rust-redis: A Redis client library written in pure Rust. Thanks to the new
rust
, 2013, at 11:37 AM, Stefan Plantikow
stefan.planti...@gmail.com wrote:
Hi,
Am 17.12.2013 um 20:10 schrieb Corey Richardson co...@octayn.net:
On Tue, Dec 17, 2013 at 2:06 PM, Stefan Plantikow
stefan.planti...@gmail.com wrote:
Hi,
Am 09.12.2013 um 16:53 schrieb Damien Radtke damienrad
The reason the Iterator suffix was removed is because when when one is
required to write the type signature it becomes hugely annoying to
keep writing Iterator all the time. Personally I think Alex's idea is
a good way forward.
On Sat, Dec 21, 2013 at 4:35 PM, Kevin Cantu m...@kevincantu.org
Hey all,
#11041 just landed, which changes the pkgid attribute to crate_id.
It's a very straightforward transition, but probably inconvenient,
especially for the rust-ci users. With it also landed the
--crate-name, --crate-id, and --crate-file-name flags to rustc, which
will print out those
On Tue, Dec 17, 2013 at 2:06 PM, Stefan Plantikow
stefan.planti...@gmail.com wrote:
Hi,
Am 09.12.2013 um 16:53 schrieb Damien Radtke damienrad...@gmail.com:
I have no idea if it would be feasible in the standard library, but wouldn't
the ideal solution be having one function (e.g.
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.
On Fri, Dec 13, 2013 at 8:14 PM, Liigo Zhuang com.li...@gmail.com wrote:
What is the distinction of package
I'm in favor of this but it makes things less pretty. Is the choice
really between pretty and fast?
On Fri, Dec 6, 2013 at 3:41 PM, Simon Sapin simon.sa...@exyr.org wrote:
We have some functions and methods such as
No, since it isn't known which trait the method should come from. It
could list *all* the traits that provide that method with that
signature, but even that wouldn't be great if you had the signature
off.
On Thu, Dec 5, 2013 at 3:26 PM, Philippe Delrieu
philippe.delr...@free.fr wrote:
I found my
How about method `foo` no found and no trait in scope provided one ?
On Thu, Dec 5, 2013 at 4:29 PM, Philippe Delrieu
philippe.delr...@free.fr wrote:
Perhaps the error message can be more explicit like trait not found for
method instead of method not found.
Le 05/12/2013 21:57, Corey
Very well for the Python community, too; there's a python-tutor list
whose sole focus is helping newbies effectively.
On Tue, Dec 3, 2013 at 5:32 PM, Martin DeMello martindeme...@gmail.com wrote:
In practice this has worked out well for the ocaml community - there's an
ocaml-beginners mailing
The compiler still handles it, and there are still tests for it. I
think it's more of a not 1.0 priority, than anything else.
On Mon, Dec 2, 2013 at 11:31 PM, Kevin Cantu m...@kevincantu.org wrote:
When I started my old Rust PPA (now superseded), the first user to
email me was an engineer from
On Sat, Nov 30, 2013 at 8:51 PM, Florian Zeitz flo...@babelmonkeys.de wrote:
Personally I would suggest calling this operator `box`, since it boxes
its argument into a newly allocated memory box.
I really like this proposal. I've watched this thread and the original
`new` proposal with
On Sat, Nov 30, 2013 at 9:30 PM, Kevin Ballard ke...@sb.org wrote:
I'm still very much a fan of leaving ~ as the allocation operator. Despite
what Patrick says, I'm pretty sure the reason why users are confused about it
is purely due to sub-par documentation, and not due to any actual
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 Rust Suggestion).
Last week was very slow, but
On Sat, Nov 30, 2013 at 10:28 PM, Patrick Walton pcwal...@mozilla.com wrote:
On 11/30/13 7:25 PM, Michael Letterle wrote:
I've got to say that the do syntax is one of the things that
appeals to me about Rust, and will probably appeal to the people
that Steve Klabnik is drawing to
I experimented with LZ4. https://github.com/mozilla/rust/pull/6954. It
isn't worth it, IMO.
On Fri, Nov 29, 2013 at 1:51 PM, Carter Charbonneau zcart...@gmail.com wrote:
Why not lz4? It's faster than snappy.
On Nov 29, 2013 11:29 AM, Patrick Walton pcwal...@mozilla.com wrote:
On 11/29/13
5+ minutes isn't bad, actually. On my (fairly beefy) desktop building
stage1 takes about that long. There isn't really too much to do to
help with compile times right now, unfortunately :( The only advice I
have is don't bootstrap: use the stage1 make targets. Their names
slip my mind, so someone
Hey fellow Rusties,
We have a fair number of new contributors, and my devious mind wonders
how we can get more. My first thought was a new tag, E-mentored, where
someone can volunteer to mentor someone through an E-easy issue. It's
a very lightweight, non-formal process, and can hopefully give
1 - 100 of 244 matches
Mail list logo
