On Thu, Jan 30, 2014 at 2:20 PM, Tony Arcieri wrote:
> On Thu, Jan 30, 2014 at 11:26 AM, Tim Chevalier
> wrote:
>>
>> In the interest of documentation (especially for the benefit of
>> whatever person or people end up writing the next package manager),
>>
gt; Tony Arcieri
>
> _______
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"If you are silent about your p
two pitfalls:
>> 1) read-bump
>> 2) ambiguity.
>>
>> AFAIK you did a remarkable good job so far, and i have all the faith
>> you are considering all arguments before coming to a decision.
>>
>> Even if some thoughts of the thoughts come form the bad smelling
>> "lurker"-
ing to split my repository up just
>> because rustpkg wasn't designed to handle that case.
>>
>> All of those points would be solved by having an explicit package
>> description file/script which was THE overarching design non-goal of
>> rustpkg. After that was made clear to me, I just ditch
t;> https://mail.mozilla.org/listinfo/rust-dev
>>
>>
>>
>> ___
>> Rust-dev mailing list
>> Rust-dev@mozilla.org
>> https://mail.mozilla.org/listinfo/rust-dev
>>
>
>
> ___
> Rust-dev
love stickers and I definitely want a Rust
> sticker :D
>
>
>
> --
> Flavio (@flaper87) Percoco
> http://www.flaper87.com
> http://github.com/FlaPer87
>
> ___
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org
>
> Patrick
>
> [1]:
> https://groups.google.com/forum/#!topic/mozilla.dev.platform/WjcCfckml4A
>
>
> _______
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
--
Tim Chevalier *
com/ directory where they
> develop their software?
>
> -SL
> ___
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in
erson, and Jack Moffitt -- for helping many people
apply for the program, and to the Mozilla coordinator for OPW, Larissa
Shapiro, for their efforts.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"If you are silent about your pain, they'll kill yo
The list is no longer on moderation. Posts from subscribers should go
through to the list without moderator intervention now.
Sorry for any inconvenience.
Cheers,
Tim
On Tue, Nov 12, 2013 at 10:10 AM, Tim Chevalier wrote:
> I've placed the list on full moderation for now, which will h
2, 2013 at 9:43 AM, Tim Chevalier wrote:
> Hi folks --
>
> I already requested that this thread end, and from here on I'm going
> to place anyone who replies to this thread further (with the same
> subject line or quoting anything from the same thread) on temporary
> modera
).
>
> --
> Please do not email me anything that you are not comfortable also sharing
> with the NSA.
>
>
> ___
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
--
Tim Chev
ight choice.
>
> With that said, though, Rust is a new and exciting language; if you can
> think of improvements, try coding them up and see what you get! In my
> experience, the Rust developers are always happy to hear from volunteers who
> are excited about the language and have concrete pull reques
y because these
>> languages/dialects did not exist at the time).
>>
>> What about Lua, which is more C-like?
>>
>> Or CoffeeScript?
>>
>> Looking at the "Influenced By" section on Wikipedia seems to indicate that
>> the answer to these questio
>>
>> Also, is it at all possible, in the long term maybe, to consider letting
>> the compiler choose where to store, in cases where a possible pointer is
>> meaningless, that is it does not express a true reference (shared object,
/
>
> --
> Please do not email me anything that you are not comfortable also sharing
> with the NSA.
>
>
> ___
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
--
Tim Chevalier * http
file :-)
With hope, the central package database (
https://github.com/mozilla/rust/issues/10041 ) will obviate the need
for this list, but in the meantime, let's maintain the list
informally.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"If you a
er pleasure, with no immediate external reward.
I'll still be on the mailing list and IRC channel, so this isn't
goodbye. If you're interested in what I'm up to next, I'll probably be
keeping track of it on my blog ( http://tim.dreamwidth.org/ ).
Cheers,
Tim
--
Tim Chevalie
ailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"If you are silent about your pain, they'll kill you and say you enjoyed it."
-- Zora Neale Hurston
___
gt; not.
>
> Anyways i am really excited about rust i hope to find some way i can
> contribute back thanks.
>
> --Phil
>
> ___
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
have some ideas
> or suggestions?
> I plan to use that for activities besides lectures and later for my bachelor
> work. But then it's nice if it's something that academics/professors sees as
> something meaningful.
>
> Anyway, thanks!
>
>
> ---
> Ilmārs Cīrulis
>
that as your case
study, you will implement your approach as part of the Rust compiler.
Then even if you don't have a finished solution at the end, you can
write about your experiences.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Being
age
collection (including code in external libraries that's called by your
code).
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Being queer is not about a right to privacy; it is about the freedom
to be public, to just be w
/2013/Rust%3A_A_Friendly_Introduction
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Being queer is not about a right to privacy; it is about the freedom
to be public, to just be who we are." -- anonymous, June 1990
Hi all--
I thought it was worth it to write up a wiki page with guidelines for
submitting Rust bugs:
https://github.com/mozilla/rust/wiki/HOWTO-submit-a-RUST-bug-report
Please edit and improve!
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"
e `rustlings` directory.
I tested the latter option with rustpkg as built from 7ddcd2, and it worked.
Feel free to ask again here if you have more questions (and I'll try
to answer them sooner :-)
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in
you be in? Would one day work better than
> another? I'll be in Santa Clara, CA, and I'm free all the evenings.
I'll be in Toronto; will anyone from the community be there?
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Being qu
o way for users to define new ones), and given
the history of `$` in Haskell, I don't see a particular reason to make
an exception.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Being queer is not about a right to privacy; it is about th
I broke this with a recent change to rustpkg from a few days
ago, and because we don't have automated tests that use the network,
the regression wasn't caught.
As a workaround for now, you can manually check the repo into a local
workspace that's in your RUST_PATH. Sorry about that
I don't know what the bug with the docs is, but in the meantime, you
can build without the docs by doing:
./configure --disable-docs
and then rebuilding.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Being queer is not about a right to p
of rustc, but that most people want to change
> it. Is that true, and when can we expect a fix?
I'm not sure that most people want to change it. Handling the issue in
general is quite subtle (see
http://web.cecs.pdx.edu/~jgmorris/pubs/morris-icfp2010-instances.pdf
). One workaround is to use new
formance numbers, memory
> usage) and some cookbook patterns could be quite helpful.
This would make a great topic for a blog post -- perhaps someone has
even already written it! As far as existing code examples go,
extra::treemap might be a good one to study.
Cheers,
Tim
--
Tim Chevali
y the same
struct.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Being queer is not about a right to privacy; it is about the freedom
to be public, to just be who we are." -- anonymous, June 1990
___
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
7;d
like to work on, even it's assigned to me (catamorphism on github),
feel free to just leave a comment and ask if it's available to work
on.
Feel free to ping me on IRC (tjc) with questions.
Thanks,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
&
what you learn.
There are only a few rusti bugs in the issue tracker --
https://github.com/mozilla/rust/issues?direction=desc&labels=A-rusti&milestone=&page=1&sort=created&state=open
-- but I'm sure you will discover more issues to fix as you start
diving into the code.
C
^~~
> error: aborting due to 6 previous errors
>
> I used, until yesterday, Rust 06 and it was all ok.
> Any ideas on how to fix this problem?
In Rust 0.7 you have to import standard library modules explicitly. If
you add the following line at the beginning:
use
poser [1] - a PHP dependency manager - for the last
> two years. It is - much like rustpkg - fully VCS-based when it comes to
> finding package releases, so I hope I can at least help on a higher
> level. If you want to discuss anything feel free to ask, I'm also on IRC
> as Selda
. (Perhaps
other people who have been in projects with internationalized
documentation can comment on the best approach(es) to this issue?)
Thanks,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Not a riot, it's a rebellion." -
just fetch the sources:
>
> rustpkg fetch
>
Planned -- see https://github.com/mozilla/rust/issues/7242
Also, I opened https://github.com/mozilla/rust/issues/7447 for Zack's
suggestions about versions.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, neve
methods for WebCam and Cat are
omitted, and presumably Cat has some fields that I left out because
they're not needed for understanding the problem. In particular, Cat
could have fields that are non-copyable, even if its constructor
returns a Cat (and not a ~Cat).
Thanks for your interest!
when I programmed in Haskell -- I found using higher-order functions
directly to be much more natural -- but that part is just my opinion.)
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Not a riot, it's a rebellion." -- Boots Riley
"At
commend listening to
the recording of the conference talk instead -- it will doubtless
benefit from feedback received during the practice talk :-)
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Not a riot, it's a rebellion." -- Boots Riley
&
I don't think there are many other languages
> able to represent something like statically freezable mutable
> containers.
This is a great suggestion as well. I don't know why iterators didn't
occur to me as a potential example; they almost stand alongside traits
and borrowed pointe
Rust can do. I had hoped some
of the test cases under bench/ might be good for this, but many of
them are written in fairly old-style Rust.
Thanks in advance, and I'll certainly acknowledge in the talk anybody
who points me to a good example.
Cheers,
Tim
--
Tim Chevalier * http://catam
to it:
fn add_equal(x: &mut Complex, y: Complex) { ...
Of course, that means that at the call site, you will have to write
something like add_equal(&mut c, copy c).
Unless you want to write a function that just takes one argument and
doubles it, like Abhijeet suggested, I don't k
ve used assigning-to-myself as a way of
signaling "I intend to work on this", but more recently people have
implied that you should only take a bug when actively working on it.
Either is ok as long as it's made explicit).
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Of
before/after. Other Rust
team members (but not me) will be at OSCON in July. If a meetup
happened to be when I was in town, I'd be happy to show up!
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Not a riot, it's a rebellion." -- Boo
nation/ and
http://genderqueerid.com/what-is-gq ).
If anyone wants to discuss this point further, please *reply sender*
and email me privately, rather than replying to the list.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Too much to carry, t
GitHub
> API provides "mergeable" attribute for this.
Thanks! I filed these enhancements in the bors issue tracker (which is
private right now for security reasons).
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Too much to carry, to
On Sat, May 4, 2013 at 3:55 AM, james wrote:
> On 01/05/2013 01:25, Tim Chevalier wrote:
>
> Let's drop this thread, as per the code of conduct at
> https://github.com/mozilla/rust/wiki/Note-development-policy :
>
> "Please keep unstructured critique to a minimum. I
ttern
binding muddies the waters (besides the ambiguity).
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Too much to carry, too much to let go
Time goes fast, learning goes slow." -- Bruce Cockburn
___
Let's drop this thread, as per the code of conduct at
https://github.com/mozilla/rust/wiki/Note-development-policy :
"Please keep unstructured critique to a minimum. If you have solid
ideas you want to experiment with, make a fork and see how it works."
Cheers,
Tim
--
Tim C
ns in Rust, but that was
removed recently. It originally existed for typestate (a feature we
removed a while ago) and more recently to assist the borrow checker.
We removed it because in Rust, it was impractical to define an
easily-checkable pure subset of the language. Bringing it back in is
somewh
y do with gdb. It's useful to know that if you
set a break on upcall_fail , then you'll break at any point where your
program calls the fail!() macro or has an assertion failure arising
from assert!().
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never
es of opinion and
that every design or implementation choice carries a trade-off and
numerous costs. There is seldom a right answer."
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Too much to carry, too much to let go
Time goes fast, learning
?
>
It doesn't exist as far as I know, but would be great to have for
Rust, and it probably wouldn't be hard to modify rustdoc to do it.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Too
heers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Too much to carry, too much to let go
Time goes fast, learning goes slow." -- Bruce Cockburn
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozil
flag that will warn you about it.)
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Too much to carry, too much to let go
Time goes fast, learning goes slow." -- Bruce Cockburn
___
Rust-dev mailing
the community, there's a possibility (I can't
promise anything) that we could put our name on it, as Mozilla.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Too much to carry, too much to let go
Time goes fast
Globs don't always work well / predictably right now. The most common
reason why something wouldn't work is a cyclic import.
If you can minimize this at all, reporting an issue would be great! Thanks!
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, neve
? Should A-regions be renamed A-borrowck?
>>
>> I think so, yes.
>>
>> Thanks for bringing this up. We didn't get to discussing triage at the
>> meeting in much detail, but we definitely need to think/talk/act a bit
>> more about it. I'll try to org
On Tue, Feb 5, 2013 at 10:52 AM, Tim Chevalier wrote:
> On Tue, Feb 5, 2013 at 10:50 AM, Brian Anderson wrote:
>> Greetings, folks,
>>
>> There was some discussion about bug triage in the meeting today so I went to
>> do some and was reminded of how frustrated I get
ollector
> A-github
I actually support breaking up the A-typesystem label into fewer
labels. I find myself using typesystem a lot when I want something
more specific, actually.
Sounds good otherwise.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in
:len(**line), where line.len() would be more idiomatic (and
because of auto-dereference, you're saved from writing the asterisks).
I'll let others point out other nits :-)
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Too much to carry, too m
aving
> mutability depend on the containing slot, could that be a source of some of
> the issues in the code?
No, not in this case.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Too much to carry, too much to let go
Time goes fast, learning
ust not being
> terribly precise in avoiding them when building the package.
I added this to the FAQ, btw:
https://github.com/mozilla/rust/wiki/Doc-usage-FAQ
and would welcome any suggestions from anyone as to how to organize
the FAQs on the wiki better; they're not the easiest thing
LLVM has infrastructure for
this kind of profile-guided optimization already, I really don't know.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Too much to carry, too much to let go
Time goes fast, l
ot particularly difficult, though, and then we could make an
informed decision about whether or not to go down this path. A lot of
the work for incremental compilation will likely also be useful for
parallelizing the compiler. So I don't see it as a waste of time.
Cheers,
Tim
--
Tim Chevalie
I suspect this is a borrowck bug (or at least shortcoming), but I
don't know the borrowck rules well enough to say for sure. I suggest
filing this code as an issue.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"We know there'd hard
Can you post the code that doesn't work? I have an idea of what might
be going on, but it's easier for me to explain if I see the code
you're trying to compile :-)
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"We know there&#
wrong or need improvement. The list or
IRC is great for asking questions where you don't think there's a
compiler bug. So you're doing it right :-)
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"We know there'd hardly be no one i
let result = self.code();
(Warning: not tested.) I believe the way to do this is to write:
let result = (self.code)();
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"We know there'd hardly be no one in prison / If
Built for me without a hitch: Mac OS X 10.7.3, uname -a says: Darwin
Tims-MacBook-Pro.local 11.3.0 Darwin Kernel Version 11.3.0: Thu Jan 12
18:47:41 PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64 x86_64
SHA1(rust-0.5.tar.gz)= 7d818abf16c0061278658b8cfc6e0e0859885b5f
Cheers,
Tim
--
Tim
ki.fi/rust-temp/
> . (As you can see, array and object referencing is very much not
> done.)
>
That's great! Maybe we don't need `break` out of `for` loops after
all... (though there is an open issue on it:
https://github.com/mozilla/rust/issues/4131 )
Cheers,
Tim
--
Tim Chev
or syntax changes. The focuses right now
are on completing the few remaining features that aren't done, library
development, and performance.
Cheers,
Tim (Rust core team member)
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
'Wouldn't you
This would be nice as a lint pass. Feel free to file it as an
enhancement request:
https://github.com/mozilla/rust/issues/new
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
'Wouldn't you rather be anything other than the kid who runs arou
la.org/listinfo/rust-dev
>
>
>
> ___
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
'Wouldn&#x
n of haskell-cafe for off-topic-ish
discussions (or, in fact, anybody could, on Google Groups). But for
now, please try to keep discussions on this list narrowly focused.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
'Wouldn't you rather be anyth
ine
> 705.
> Abort trap: 6
>
> Clearly, this code is nonsensical since there is no implementation of the
> trait "Text". Should the compiler produce a different message?
>
Yes, this is a compiler bug. Would you mind filling out an issue report at:
https://github.com/mozilla/rust/
st.psu.edu/viewdoc/summary?doi=10.1.1.48.5674
("Interfaces" have been renamed to "traits" in the soon-to-be-released
Rust 0.4 release, by the way; it looks like you may be looking at the
docs from Rust 0.3.)
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in e
27;m using to
> building software in another language with typeclasses (Scala). I'm
> still looking for the zen of Rust OO.
>
> I ran into some old blog posts that discuss a class keyword but I
> wasn't able to make those examples run in 0.3.1. Do we only have impls
> now
A simple way to do it is with option types:
fn a(x: ~str, y: option<~str>) -> ~str {
/* do whatever */
}
fn a_1(x: ~str) -> ~str {
a(x, none)
}
You may be able to use traits and impls to overload the name a, but if
you don't mind giving the different functions different names, t
at doesn't mean we can't support tail calls
just for the special labelled break/continue form.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Debate is useless when one participant denies the full dignity of the
other." -- Eric Bern
if foo was an enum. We got rid of this because
Patrick said it was too hard to implement in the context of resolve3.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Debate is useless when one participant denies the full dignity of the
trust anyone who is sensible enough to choose
Rust to be sensible enough to choose those conventions for themselves
:-)
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Debate is useless when one participant denies the full dignity of the
other.&
Meeting agenda for tomorrow:
https://etherpad.mozilla.org/Meeting-weekly-2012-07-17
Add your issues!
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Debate is useless when one participant denies the full dignity of the
other." -- E
ommits from everybody else before making a small amount of progress.
Let's all try to be mindful of the happiness and productivity of
everyone else on the team :-)
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Debate is useless when one
entation in
a future release.
But as with everything we do, using it at your own risk and asking
questions on IRC is encouraged!
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Debate is useless when one participant denies
hierarchy. I don't think it's intuitive. When programmers see a module path,
> they want to have a sense where the module resides. I think the module
> hierarchy system in Haskell is a good compromise between power and
> simplicity.
>
I'm not sure I understand -- Rust has n
Since Niko is on vacation, I thought I would post link to the agenda
for tomorrow:
https://etherpad.mozilla.org/Meeting-weekly-2012-07-03
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Debate is useless when one participant denies the full digni
think this is not a change requiring
an RFC, as it's part of the long-standing class proposal, but I wanted
to check to see if anyone would object to me removing resources now.
If so, let me know.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
that
when control passes to the callee, it becomes deinitialized at the
call site. (Obviously, this means the caller has to pass an l-value.)
This does not seem to be documented, and should be.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Debate i
//github.com/mozilla/rust/issues/1726 and
https://mail.mozilla.org/pipermail/rust-dev/2011-November/000929.html
-- but that's a bit risky since parts of the latter were superseded by
ifaces/impls, which were implemented later. At least that should give
you more examples.
Cheers,
Tim
-
channel (see
https://github.com/mozilla/rust/wiki/Note-development-policy for
details) if you have more questions.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
"Debate is useless when one participant denies the full dignity of the
other." -- Eric
ink we have any plans to add implicit casts as implied by
your other 4 examples. It seems too complex -- if any of the variables
in your example were mutated after being initialized, the pass that
would insert these casts would get pretty complicated.
Cheers,
Tim
--
Tim Chevalier * http://catamor
t an
error.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
“I cannot hide my anger to spare you guilt, nor hurt feelings, nor
answering anger; for to do so insults and trivializes all our efforts.
Guilt is not a response to anger; it is a response to one’s o
> cc1plus: error: unrecognized command line option ‘-arch’
> make: *** [rt/x86_64-apple-darwin/sync/timer.o] Error 1
Can you recompile by doing "VERBOSE=1 make" and then post the output?
Thanks,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
“I can
bids local
variable names that shadow the name of a tag that's in scope.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
“I cannot hide my anger to spare you guilt, nor hurt feelings, nor
answering anger; for to do so insults and trivializes all our ef
ressing some similar problems.
Cheers,
Tim
--
Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
“I cannot hide my anger to spare you guilt, nor hurt feelings, nor
answering anger; for to do so insults and trivializes all our efforts.
Guilt is not a response to anger; it is a
1 - 100 of 106 matches
Mail list logo
