There is a rather old repo at https://github.com/Jurily/rust-c-example
I'll make it a full tutorial when I find the time.
On Tue, Apr 22, 2014 at 3:17 AM, Doug wrote:
> Just my $0.02; totally agree; a proper guide to linking (specifically the
> 'right' way to link when you have a crate with exte
Actually...I do not. :)
On Tue, Apr 22, 2014 at 9:05 PM, Chris Morgan wrote:
> On Wed, Apr 23, 2014 at 10:35 AM, Thad Guidry
> 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
> “oxi
On Wed, Apr 23, 2014 at 10:35 AM, Thad Guidry 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
Rust-dev@mozilla.o
It's easy to submit a pull request, for a git programmer. My difficulty is
the weak of English level to write a so long rfc.
2014年4月23日 上午5:57于 "Tommi" 写道：
> On 2014-04-22, at 21:44, Brian Anderson wrote:
>
> I'm not sure what you are asking for here. Have you submitted this as a
> pull request t
I would have named it ... "oxide" instead of zinc ;-) ... rust = iron oxide
On Tue, Apr 22, 2014 at 1:50 PM, Brian Anderson wrote:
> 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
Tommi (cc'ing rust-dev)-
I recommend you make a small fake github repository of your own, and learn the
github workflow directly by forking that (perhaps with a separate fresh dummy
github user account).
I am not being facetious; I did a lot of that when I was first getting my
bearings using g
On 2014-04-22, at 21:44, Brian Anderson wrote:
> 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?
No, I haven't made the pull request, because I don't know how to do that (or
perhaps I would know how to do that, if I kn
The complex part of the process is figuring out how GitHub works. The problem
I'm having with GitHub (as far as I can tell) is either (1) creating a fork or
(2) submitting a pull request of the fork I've created (I'm not sure). Creating
the first fork of /rust-lang/rfcs was easy: I just clicked
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 ref
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, T
Just my $0.02; totally agree; a proper guide to linking (specifically the
'right' way to link when you have a crate with external C library
dependencies), and interacting directly with ffi (str <--> char * for
example) would be extremely useful.
I've been going through the process of doing that st
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 refactoring work for LPC1768 code, so STM32F4 is
kind of broken yet, and LPC1114 is totally dropped, but I'l
2014-04-22 15:45 GMT+02:00 Tommi :
> No one?
>
> I understand that a part of the reason the RFC process is made so complex
> is that it filters out idiots like me. But I think this one is a pretty
> important design choice that Rust is about to get wrong.
>
>
If the RFC process is complex, then I
No one?
I understand that a part of the reason the RFC process is made so complex is
that it filters out idiots like me. But I think this one is a pretty important
design choice that Rust is about to get wrong.
On 2014-04-18, at 6:27, Tommi wrote:
> Could someone please commit this RFC for me
Along with the "A 30-minute intro to Rust", we also need a 1-minute and/or
5-minute intro, in rust-lang.org website.
2014年4月22日 上午7:11于 "Brian Anderson" 写道：
> Hi.
>
> I've been convinced recently that Rust is missing crucial documentation of
> a particular nature: using Rust in practice. I would l
On the related matter of reference material, ClojureDocs seems quite good
as a reference guide :
http://clojuredocs.org/
http://clojuredocs.org/clojure_core/clojure.core/reduce
and seems editable by the community.
The std API guide :
http://static.rust-lang.org/doc/master/std/index.html
is s
I agree with Corey, it's much better to send it upstream first. I'd be
more than willing to help you out with writing tests or taking a peek
at the patch if you want! I'm acrichto on IRC
On Tue, Apr 22, 2014 at 12:43 AM, Vladimir Pouzanov wrote:
> The problem is that mrc is generated unless targe
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 wrote:
> The problem is that mrc is generated unless target is thumb1, but cortex-m3
> is thumb2 that still doesn't support mrc:
> http://infoce
The problem is that mrc is generated unless target is thumb1, but cortex-m3
is thumb2 that still doesn't support mrc:
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.faqs/ka398.html,
so an additional check to ST->TargetTriple.Data is required to verify it's
not thumbv7m.
Do I need to s
Thanks for the meetup,
it was nice meeting you guys.
See you next month !
2014-04-21 15:27 GMT+02:00 Axel Viala :
> That confirmed it's tonight!
>
> Third of his name.
>
> Planing:
> 18:00 -> 19:30: Lunch and informal meeting.
> 19:30 -> 23:00: Workshops for different levels.
>
> Reps Page: ht
20 matches
Mail list logo
