Did it come up as an unused-attribute warning?
No, it didn't.
The simple reason it doesn’t come up as an unknown attribute is
because it did not successfully compile, and so it did not get to the
step where it warns about unused attributes.
___
On Tue, Jul 15, 2014 at 4:16 AM, Brian Anderson bander...@mozilla.com wrote:
Can somebody file an issue described exactly what we should do and cc me?
Nothing. Absolutely nothing.
robots.txt rules do not apply to historical data; if archive.org has
archived something, the introduction of a new
On Thu, Jun 5, 2014 at 9:01 AM, Brian Anderson bander...@mozilla.com wrote:
# Date/Time (https://github.com/mozilla/rust/issues/14657)
Our time crate is very minimal, and the API looks dated. This is a hard
problem and JodaTime seems to be well regarded so let's just copy it.
I suggest that
On Wed, Apr 23, 2014 at 10:35 AM, Thad Guidry thadgui...@gmail.com wrote:
I would have named it ... oxide instead of zinc ;-) ... rust = iron oxide
Do you know how many projects written in Rust have already been named “oxide”?
___
Rust-dev mailing list
Any chance of getting arm-linux-unknown-gnueabihf builds?
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
typically been true--let this impression not
change.
I suggest very strongly that this thread cease.
-- Chris Morgan
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
You are right, it is about convenient access to the info, not the lack of
info.
I often wish I could conveniently find this information--far too often it's hard
to identify the PR when a breaking feature came in. Often I end up waiting for
Corey to publish TWiR, with all the relevant issue
The macro is being defined after the module is defined. You need to move
the macro definition before the pub mod submod; line. Also due to the
scoping rules of macros, you don't need #[macro_escape] there---it's a
child, so it gets the macro. Only siblings, parents, uncles, aunts,
cousins, c.
The macro is being defined after the module is defined. You need to move
the macro definition before the pub mod submod; line. Also due to the
scoping rules of macros, you don't need #[macro_escape] there---it's a
child, so it gets the macro. Only siblings, parents, uncles, aunts,
cousins, c.
The problem there is that `@Field` is not a type, because you haven't
specified the value for the generic constraint T. That is, the
pertinent trait object would be something like `@Fieldint`. It's not
possible to have a field without the type being specified; that is,
`get_fields()` can only be
On Oct 17, 2013 8:12 AM, Patrick Walton pwal...@mozilla.com wrote:
For a long time now I've been wanting to make unused non-unit return
values a warning. I think this would be a perfect time to do that...
I would love this to be the case. It's the biggest problem I had with Go's
error handling:
sent it just to me.]
On Fri, Oct 4, 2013 at 11:36 AM, leef huo leef...@gmail.com wrote:
Chris Morgan , thanks .
After change the windows code page to 65001,and use Lucida console fonts,
there was a slight improvement, the output becomes:
but still have problems,it is not entirely correct
When you're using Command Prompt, you're basically stuck. It doesn't
have any meaningful Unicode support.
See also
http://stackoverflow.com/questions/388490/unicode-characters-in-windows-command-line-how
On Thu, Oct 3, 2013 at 12:50 PM, leef huo leef...@gmail.com wrote:
I want to print hello
an implementation mostly complete in my
augmented-assignment branch
(https://github.com/chris-morgan/rust/compare/augmented-assignment),
but even if I managed to convince the Rust side of rustc that I was
competent, LLVM called my bluff.
The last state of my branch and what appears to be wrong
Your example looked like it should be correct, but I'm not going to
figure out why it's not working, because extra::net no longer exists
in the Rust development head.
Here is an example using the new runtime TCP library, which is
currently in std::rt::io::net.
Whether it compiles on Rust 0.7 or
There seems to be a basic assumption of ASCII identifiers. Hey, this
ain't the eighties!
Let's have us an XᴍʟHᴛᴛᴘRequest. Absolutely clear with no scope for
misunderstanding in either direction: Gᴄ; Rᴄ; Aʀᴄ; SimpleHᴛᴛᴘServer.
Monospace font support is a little poor, but I'm sure they'll fix that
16 matches
Mail list logo
