Hello
I'm willing to help on this task, I think having a good completion library
can help a lot smoothing the learning curve of a new language. I learned
python in a few days with aptana, and I remember a few years ago how it was
easy to write C++ with visual studio. Having an IDE integration is
hello
Where can I find an exhaustive list of the keywords defined by the
language? I want to add basic syntax highlighting support to the rust
language to some web editors and I don't know all of them yet.
Thanks.
-
Gaetan
___
Rust-dev mailing
http://static.rust-lang.org/doc/master/rust.html#keywords
Cheers,
Josh
On 19 November 2013 17:06, Gaetan gae...@xeberon.net wrote:
hello
Where can I find an exhaustive list of the keywords defined by the
language? I want to add basic syntax highlighting support to the rust
language to
On Tue, Nov 19, 2013 at 5:17 AM, Patrick Walton pcwal...@mozilla.com wrote:
I've observed a lot of beginning Rust programmers treat the language as add
sigils until it works. (I have specific examples but don't want to name
people here; however, feel free to contact me privately if you're
Is there any specific issue with the current tutorial section on
boxes? It mentions every case where owned boxes are useful.
http://static.rust-lang.org/doc/master/tutorial.html#boxes
I keep hearing that it should be better, but have yet to see any hints
on where it falls short. It's not going
On Tue, Nov 19, 2013 at 4:12 AM, Josh Matthews j...@joshmatthews.net wrote:
http://static.rust-lang.org/doc/master/rust.html#keywords
Cheers,
Josh
That's missing `proc`, at the very least :). Perhaps it would be best
to look at `libsyntax/parse/token.rs`. Just ignore __LogLevel (it
existing
On Mon, Nov 18, 2013 at 6:25 PM, Gokcehan Kara gokcehank...@gmail.com wrote:
1) Implement a type under cursor functionality
rustfind (https://github.com/dobkeratops/rustfind) does this and more,
for crates that compile.
Some more general questions are;
- How feasible is this project with the
That was my point on another thread. I think it's best to have a top-bottom
approach, ie, decribe everything else BUT the language first (how crates
works, how to compile, how to test,...) and then introduce the memory
concepts, etc.
I think the technical writer is a full time job, how to present
I don't think there is any particular issue with the tutorial, but we need
more recipes on how to handle typical situations.
-
Gaetan
2013/11/19 Daniel Micay danielmi...@gmail.com
Is there any specific issue with the current tutorial section on
boxes? It mentions every case where
On 19 November 2013 11:20, Daniel Micay danielmi...@gmail.com wrote:
On Tue, Nov 19, 2013 at 4:12 AM, Josh Matthews j...@joshmatthews.net
wrote:
http://static.rust-lang.org/doc/master/rust.html#keywords
Cheers,
Josh
That's missing `proc`, at the very least :). Perhaps it would be best
can you give a little review?
https://github.com/Stibbons/crayon-syntax-rust
-
Gaetan
2013/11/19 Daniel Micay danielmi...@gmail.com
On Tue, Nov 19, 2013 at 4:12 AM, Josh Matthews j...@joshmatthews.net
wrote:
http://static.rust-lang.org/doc/master/rust.html#keywords
Cheers,
Josh
On Sun, Nov 17, 2013 at 2:08 AM, Niko Matsakis n...@alum.mit.edu wrote:
On Fri, Nov 15, 2013 at 05:05:28PM +0100, Gábor Lehel wrote:
I have some ideas about typey things and I'm going to write them down. It
will be long.
I haven't read this all yet, I just want to respond to the first few
In the french presentation for rust 0.8 [1], the author gives the analogy
with C++ semantics
- ~ is a bit like unique_ptr
- @ is an enhanced shared_ptrT
- borrowed pointer works like C++ reference
and I think it was very helpful to better understand them. I don't know if
it is true or now, but
On 19/11/13 20:51, Gaetan wrote:
In the french presentation for rust 0.8 [1], the author gives the
analogy with C++ semantics
- ~ is a bit like unique_ptr
- @ is an enhanced shared_ptrT
- borrowed pointer works like C++ reference
and I think it was very helpful to better understand them. I
On Tue, Nov 19, 2013 at 4:51 AM, Gaetan gae...@xeberon.net wrote:
In the french presentation for rust 0.8 [1], the author gives the analogy
with C++ semantics
- ~ is a bit like unique_ptr
- @ is an enhanced shared_ptrT
- borrowed pointer works like C++ reference
and I think it was very
In case this helps, I recently noticed that the sigils correspond to
possessive pronouns:
'~' = my,
'' = their,
'@' = our
Of course, `@` might be going away, but `Rc`, `Gc`, and so forth all
(will) have the same intuitive content, only different representations
(among other
Can I advise to have a certain constitency in the semantics?
Not having ~foo, *foo, Rc, Gc.
I would rather prefere having
~foo *foo foo @foo
of
Somethingfoo, otherfoo, Rc foo
By the way, I like pretty much your pronoums thing, this help understanding
:)
-
Gaetan
2013/11/19 Gábor
On Tue, Nov 19, 2013 at 5:56 AM, Gaetan gae...@xeberon.net wrote:
Can I advise to have a certain constitency in the semantics?
Not having ~foo, *foo, Rc, Gc.
I would rather prefere having
~foo *foo foo @foo
of
Somethingfoo, otherfoo, Rc foo
By the way, I like pretty much your
On 11/19/2013 12:09 PM, Daniel Micay wrote:
The `loop` keyword still exists for the moment, but only for infinite
loops. I'd prefer removing it and just using `while true { ... }`.
My view on conditionned loop is something like:
loop [while cond] {
...
[continue if cond]
...
On 11/19/2013 10:12 AM, Jordi Boggiano wrote:
Often there is an alternative
to pooping sigils all over the code, but if you don't understand the
concepts behind it it's hard to reason about what those alternatives
could be.
+++
This is what I'm asking for about pointer variety and memory
On 11/19/2013 10:51 AM, Gaetan wrote:
In the french presentation for rust 0.8 [1], the author gives the analogy
with C++ semantics
- ~ is a bit like unique_ptr
- @ is an enhanced shared_ptrT
- borrowed pointer works like C++ reference
and I think it was very helpful to better understand them. I
On Tue, Nov 19, 2013 at 6:45 AM, spir denis.s...@gmail.com wrote:
This helped me too, even if I'm not a C++ programmer (can only read).
However, it is still not enough to understand the meaning of each of those
pointer varieties, imo (at least, _i_ still don't get it). What semantic
kinds of
On Tue, Nov 19, 2013 at 6:42 AM, Gaetan gae...@xeberon.net wrote:
I d prefere letting do launch tasks and don t add confusion.
Tasks are part of the standard library, and don't have any presence at
a language level.
___
Rust-dev mailing list
+1 semantics is so important
Le 19 nov. 2013 12:22, spir denis.s...@gmail.com a écrit :
On 11/19/2013 10:12 AM, Jordi Boggiano wrote:
Often there is an alternative
to pooping sigils all over the code, but if you don't understand the
concepts behind it it's hard to reason about what those
On 19/11/13 05:17, Patrick Walton wrote:
I've observed a lot of beginning Rust programmers treat the language as
add sigils until it works. (I have specific examples but don't want to
name people here; however, feel free to contact me privately if you're
curious.) They end up with slow
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 in a tutorial.
You don't do this every day :)
-
On 19/11/13 02:36, Nathan Myers wrote:
Rust is a general purpose language designed to make programming
more fun for the serious programmer.
- nobody, yet.
Honestly, I don't really care about fun. What my company needs is more
in line with:
« Rust is a powerful, clean, easy-to-learn and
On Tue, Nov 19, 2013 at 7:27 AM, Gaetan gae...@xeberon.net wrote:
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
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 for recursive types, which is almost the only use case
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 use another semantic.
However, I don't see
On Tue, Nov 19, 2013 at 7:35 AM, spir denis.s...@gmail.com 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 are ~ pointers in every corner
of
On Tue, Nov 19, 2013 at 7:40 AM, Gaetan gae...@xeberon.net wrote:
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
Sorry, I rephrase: Let do spawn high level functions like each or
spawn and not confuse it with loop or while.
-
Gaetan
2013/11/19 Daniel Micay danielmi...@gmail.com
On Tue, Nov 19, 2013 at 6:42 AM, Gaetan gae...@xeberon.net wrote:
I d prefere letting do launch tasks and don t add
On Tue, Nov 19, 2013 at 7:49 AM, Gaetan gae...@xeberon.net wrote:
Sorry, I rephrase: Let do spawn high level functions like each or
spawn and not confuse it with loop or while.
-
Gaetan
Ah, my fault for taking that out of context. I should have read the
parent email :).
I think it is one of the first thing to explain, actually...
Playing with strings, using the method in std or extra requires to
understand it. I wanted to use (and improve) extra::url and others (like
std::path,...) and... I was simply lost with all of these ~str... and
nothing in the manual or
On Tue, Nov 19, 2013 at 7:52 AM, Gaetan gae...@xeberon.net wrote:
I think it is one of the first thing to explain, actually...
Playing with strings, using the method in std or extra requires to
understand it. I wanted to use (and improve) extra::url and others (like
std::path,...) and... I
Sorry, but it's not clear.
the only occurences of ~str are in Declaring and implementing traits
section...
Maybe by adding more string specific examples would help...
And a special section one why ~str is not a ~T would be so useful!
-
Gaetan
2013/11/19 Daniel Micay danielmi...@gmail.com
However, I want to highlight it is really appreciable that you, the rust
team, are so open to our question.
Just wanted to give you this feedback, I don't want to be held like the guy
who criticize the current work, I know very much that is could be very
annoying.
Just willing to help :)
-
Hello,
I would like to share my experience about the Rust doc and the tutorial.
I've just started to learn Rust and I've decided to use it on a project
I work on. Like everybody I read the Rust tutorial. It's not a really a
tutorial for beginner but it do a good job in presenting Rust and its
I think it's better to enhance the extra::json lib itself and write proper
module documentation, with samples, use case etc.
My reference is the QT documentation. You never open and samples or even
the QT source code, everything is in the module documentation.
-
Gaetan
2013/11/19 Philippe
Also, what we set up in our scrum team is targetted doc stories inside
each sprint.
Let's say that over the next month, the objective is to improve a set of
module doc, ie, a list of very useful std or extra lib that is not properly
documented.
For instance, the next month we target on improving
I am willing to help also but i find it quite hard to setup the
environnement properly. Is these a tutorial for this point?
Le 19 nov. 2013 14:58, Philippe Delrieu philippe.delr...@free.fr a
écrit :
I'am ok to add sample code in json.rs.
how can I do?
I think I will have other sample code for
I'am ok to add sample code in json.rs.
how can I do?
I think I will have other sample code for other lib in a few days. I'll
wait that the lib is open to doc enhancement or I put it as it come and
how can it be managed.
Philippe
Le 19/11/2013 14:48, Gaetan a écrit :
Also, what we set up in
On 11/19/13 3:09 AM, Daniel Micay wrote:
The `loop` keyword still exists for the moment, but only for infinite
loops. I'd prefer removing it and just using `while true { ... }`.
The liveness analysis uses the infinite nature of `loop`, and it was
felt that special-casing the `true` boolean
I am a student and thinking to write tutorial for it .
* Laxmi Narayan Patel*
* MCA NIT Durgapur ( Final year)*
* Mob:-8345847473*
On Tue, Nov 19, 2013 at 10:33 AM, Thad Guidry thadgui...@gmail.com wrote:
I tend to agree with this, think that a
On 11/18/2013 06:22 PM, Alex Crichton wrote:
* #[link(...)] becomes the new method of specifying linkage semantics on extern
blocks, and it may be used similarly to link_args today
I'd kind of like for this to be available at the crate level too since most
libraries don't use OS X two-level
On 11/18/2013 08:01 PM, Zack Corr wrote:
On Tue, Nov 19, 2013 at 11:13 AM, Brian Anderson
bander...@mozilla.com mailto:bander...@mozilla.com wrote:
Of course this conflicts with the `link` attribute of crates,
which I think is poorly named anyway.
Perhaps #[link] in its current usage
On Nov 19, 2013, at 3:08 AM, Daniel Micay danielmi...@gmail.com wrote:
I wouldn't mind not having `~T` in the language at all, but am not
really opposed to including it because there's no harm. Choosing to
special-case arbitrary non-trivial data structures like vectors and
reference counted
Good documentation is crucial for the success of a language. Some friends
of mine simply ceased their efforts on a language due to lack of good docs
about it. There are examples: excellent languages, as Falcon, Gosu, Fantom,
probably do not have sufficient resources to produce what their value
I still struggle with the json API. I try it using encode and decode API
and I face a problem.
I take this code in the json test case :
let m = @mut MemWriter::new();
f(m as @mut io::Writer);
and I have an error :
The managed box syntax will be replaced by a library type, and a
I'm willing to help on this task, I think having a good completion library
can help a lot smoothing the learning curve of a new language. I learned
python in a few days with aptana, and I remember a few years ago how it was
easy to write C++ with visual studio. Having an IDE integration is
I'm willing to help on this task, I think having a good completion library
can help a lot smoothing the learning curve of a new language. I learned
python in a few days with aptana, and I remember a few years ago how it was
easy to write C++ with visual studio. Having an IDE integration is
On 11/19/13 11:48 AM, Philippe Delrieu wrote:
I still struggle with the json API. I try it using encode and decode API
and I face a problem.
I take this code in the json test case :
let m = @mut MemWriter::new();
f(m as @mut io::Writer);
and I have an error :
The managed box
I think we can write in rust and perhaps reuse part of the compiler, but we
cannot allow to support only fully compiler crates.
It may be possible to begin a draft in language such as python
(YouCompleteMe seems to be written mostly in python)
-
Gaetan
2013/11/19 Gokcehan Kara
I will be speculating a little since I haven't actually read the source. As
far as I understand, YouCompleteMe uses python for some parts but at its
core it has a cpp component using libclang library. libclang library itself
is already something that provides code completion which is the thing
Hello rust-dev!
Everyone's had their fair share of issues with autoref and autoderef,
and it's worth considering removing certain portions of it from the
compiler. The discussion around this has been rooted in the past, but
has recently been brought up as part of
Additionally, we discussed this today at our weekly meeting, and the
minutes can be found here:
https://github.com/mozilla/rust/wiki/Meeting-weekly-2013-11-19#autoderef
___
Rust-dev mailing list
Rust-dev@mozilla.org
In general, I’m not a fan of *, and I like auto-borrowing (autoref sounds like
it turns T into T, not ~T into T). I understand the arguments to get rid of
it though.
BTW, you said that the current proposal still includes autoref for function
invocation. That sounds to me like autoref would
+1
在 2013年11月19日 下午8:27，Gaetan gae...@xeberon.net写道：
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
在 2013年11月19日 下午8:35，spir denis.s...@gmail.com写道：
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
在 2013年11月19日 下午8:41，Gaetan gae...@xeberon.net写道：
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,
在 2013年11月19日 下午8:44，Daniel Micay danielmi...@gmail.com写道：
On Tue, Nov 19, 2013 at 7:35 AM, spir denis.s...@gmail.com 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
Personally I would prefer if in Rust worked similar to const T in c++
In that case, you would not be able to tell whether a function argument was
passed by value or by reference. I actually like this feature about Rust
(C# has it too with the `ref` keyword).
--
Ziad
On Tue, Nov 19, 2013 at
On Tue, Nov 19, 2013 at 4:43 AM, Daniel Micay danielmi...@gmail.com wrote:
The expression ~([1, 2, 3]) has a different type than the expression
~[1, 2, 3]. The former is an owned box containing a fixed size array
(~[int, ..3]) and the latter is a dynamic array (~[int]).
The ~str and ~[T]
If the function is not going to mutate it, I don't really care if it's
by-ref or by-value. That's why I said const T, not T. Well,
except for the case when a function caches a reference to something which I
later mutate. But borrow checking will prevent that.
I would also be totally fine
While i like auto magic eg you could let region analysis work out the
pointer type , borrowed pointers etc ,however you need to be very careful
. C# uses ref but autoboxing is a major issue , you dont know when the
struct is boxed ( there are some places besides the obvious virt call ) and
then
On Tue, Nov 19, 2013 at 5:21 PM, Patrick Walton pcwal...@mozilla.comwrote:
I agree that we should change this, but give us some credit: it's only an
obvious design mistake now that we've gotten to this point.
[...]
The current status is the product of the slow evolution of a design that
On Tue, Nov 19, 2013 at 1:12 PM, Gokcehan Kara gokcehank...@gmail.comwrote:
I will be speculating a little since I haven't actually read the source.
As far as I understand, YouCompleteMe uses python for some parts but at its
core it has a cpp component using libclang library. libclang library
On 2013-11-20, at 1:40, Benjamin Striegel ben.strie...@gmail.com wrote:
If autoref still happens on methods, does this mean that you'd be able to get
around the need to do:
sort(mut *foo);
...by turning it into a method?
foo.sort();
I like how your argument nudges this whole
On 11/19/13 7:43 PM, Tommi wrote:
I like how your argument nudges this whole discussion a few inches to
the left. Now we see that disallowing auto-borrowing from regular
function arguments doesn't buy us anything unless we also disallow it
from the target of method invocation syntax (dot
On 2013-11-20, at 6:24, Patrick Walton pcwal...@mozilla.com wrote:
On 11/19/13 7:43 PM, Tommi wrote:
I like how your argument nudges this whole discussion a few inches to
the left. Now we see that disallowing auto-borrowing from regular
function arguments doesn't buy us anything unless we
On 2013-11-20, at 7:13, Tommi rusty.ga...@icloud.com wrote:
Yeah, my claim that it doesn't buy us anything stemmed from a misconception
that arg.foo() could move arg, given let arg: ~A; and fn foo(x: ~A) {...}. I
had already forgotten that Rust UFCS was specified differently from D's. To
72 matches
Mail list logo
