[rust-dev] Question about threads (that arose while trying to write a FUSE interface)

Hi Rust devs, What can I assume about the safety of having a C library spawn its own threads, from which it calls function pointers to extern functions written in rust? My guess (and only a guess--I have no actual reasoning behind it) would be something like this: * I cannot expect

[rust-dev] Iterator blocks (yield)

Hi everyone, I'm writing a series of blog posts about a possible *yield statement* for Rust. I just published the article that warrants some discussion and I'd really like to hear what you all think about the things therein:

Re: [rust-dev] Question about threads (that arose while trying to write a FUSE interface)

Hi Micah, I don't have much experience with rust but I stumbled onto a similar problem a few weeks ago. What I found out was that calling rust functions from code that have no rust-thread context will fail most often than not. Except if those functions are simple wrappers around extern c

[rust-dev] Adding else on for loops, like Python

Hi, Now that the for loop is based on external iterators, can we reconsider for-else? Proposal: for i in iter { // ... } else { // ... } The optional else block is executed when the for loop stops without exhausting the iterator, ie. when break is used. --

Re: [rust-dev] Adding else on for loops, like Python

Le 10/08/2013 15:56, Jordi Boggiano a écrit : On 10.08.2013 16:10, Simon Sapin wrote: Proposal: for i in iter { // ... } else { // ... } The optional else block is executed when the for loop stops without exhausting the iterator, ie. when break is used. Maybe

Re: [rust-dev] Adding else on for loops, like Python

In all my programming career as a python programmer I have never used a for-else construct. In fact, I won't be able to tell you exactly when the else-block is executed off the top of my head either. Even though that probably speaks more about me as a programmer than about the python language, it

Re: [rust-dev] Adding else on for loops, like Python

Le 10/08/2013 15:10, Simon Sapin a écrit : Proposal: for i in iter { // ... } else { // ... } The optional else block is executed when the for loop stops without exhausting the iterator, ie. when break is used. Typical usage is finding an element in a

Re: [rust-dev] Adding else on for loops, like Python

On 8/10/13 7:10 AM, Simon Sapin wrote: Hi, Now that the for loop is based on external iterators, can we reconsider for-else? Proposal: for i in iter { // ... } else { // ... } The optional else block is executed when the for loop stops without

Re: [rust-dev] Adding else on for loops, like Python

On 08/10/2013 07:24 PM, Paul Nathan wrote: On 8/10/13 7:10 AM, Simon Sapin wrote: Hi, Now that the for loop is based on external iterators, can we reconsider for-else? Proposal: for i in iter { // ... } else { // ... } The optional else block is executed

Re: [rust-dev] Question about threads (that arose while trying to write a FUSE interface)

On 08/09/2013 11:30 PM, Micah Chalmer wrote: Hi Rust devs, What can I assume about the safety of having a C library spawn its own threads, from which it calls function pointers to extern functions written in rust? My guess (and only a guess--I have no actual reasoning behind it) would be

Re: [rust-dev] Question about threads (that arose while trying to write a FUSE interface)

On 08/10/2013 06:27 AM, raphael catolino wrote: Hi Micah, I don't have much experience with rust but I stumbled onto a similar problem a few weeks ago. What I found out was that calling rust functions from code that have no rust-thread context will fail most often than not. Except if those

[rust-dev] Emacs mode for rusti (repl)

Hello, I wrote an Emacs mode to integrate rusti (the rust repl) into Emacs. https://github.com/ruediger/rusti.el/blob/master/rusti.el Load the file and run M-x rusti RET to open a buffer containing a rusti session. It also comes with rusti-minor-mode to add keybindings to rust-mode making it

Re: [rust-dev] Question about threads (that arose while trying to write a FUSE interface)

On Sat, Aug 10, 2013 at 6:44 PM, Brian Anderson bander...@mozilla.com wrote: Most of the standard library will work. The major things that won't are GC, task-local storage, and failure. This may or may not include logging, depending on whether it currently depends on GC and whether you use %?.

[rust-dev] This Week in Rust

content copied from http://cmr.github.io/blog/2013/08/10/this-week-in-rust/ -- Hello and welcome to the tenth issue of *This Week in Rust*. This week marks the enabling of the new runtime written entirely in Rust. A lot happens every week, so I'm going to start omitting PRs that I deem of lesser

Re: [rust-dev] Adding else on for loops, like Python

I'm a big Python user, but I'm -1 on for..else -- mostly because of the choice of the else keyword. The issue is that it's downright misleading. You don't look at the 'else' clause and think oh, I don't know what that means go look up the docs like you might with other unfamiliar parts of a new