sb0 has joined #m-labs
<
sb0>
bb-m-labs, force build --tag=0.3 migen
<
bb-m-labs>
Something bad happened (see logs)
<
sb0>
bb-m-labs, force build --revision=0.3 migen
<
bb-m-labs>
build #87 forced
<
bb-m-labs>
I'll give a shout when the build finishes
sandeepkr__ has quit [Ping timeout: 265 seconds]
sandeepkr has joined #m-labs
fengling has joined #m-labs
sb0 has quit [Quit: Leaving]
monicaleung has joined #m-labs
rohitksingh has joined #m-labs
rjo_ has joined #m-labs
awallin has quit [*.net *.split]
rjo has quit [*.net *.split]
awallin_ has joined #m-labs
monicaleung has quit [Quit: Leaving]
sb0 has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
<
whitequark>
sb0: re news: I'm not sure why you keep mentioning asyncio when I have no plans of doing anything close to it...
<
sb0>
so what do you plan?
<
whitequark>
I've just talked about it yesterday? non-preemptible threads
<
sb0>
bah that't the same
<
whitequark>
not in any meaningful way
rohitksingh has quit [Ping timeout: 276 seconds]
rohitksingh has joined #m-labs
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
<
sb0>
the implementation and syntax are certainly different but the user experience, which is mostly concerned with locking, is essentially the same
<
whitequark>
I don't expect to use locking either
<
sb0>
yes, in many cases it is not needed, which is the point
fengling has joined #m-labs
<
whitequark>
uhm, you cannot just access or mutate shared data in Rust
<
whitequark>
forbidding that is one of the reasons the language exist
<
whitequark>
in other words, it's not that I just don't expect to use locking, I don't expect to have shared mutable state
<
sb0>
there is always some shared mutable state somewhere.
<
whitequark>
yeah, like the implementation of a channel
<
whitequark>
but for purposes of the code inside the threads, whether they're preemptible or not is basically irrelevant
<
sb0>
how do you cancel the task handling the current session when a new connection is opened from another task?
<
whitequark>
I wake it up and give it a error code that means the wait was interrupted
felix_ has quit [Ping timeout: 250 seconds]
felix_ has joined #m-labs
rohitksingh1 has joined #m-labs
rohitksingh has quit [Ping timeout: 265 seconds]
fengling has quit [Ping timeout: 240 seconds]
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
rohitksingh1 has quit [Quit: Leaving.]
mumptai has joined #m-labs
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
xcombell1 has joined #m-labs
rjo_ has quit [Ping timeout: 252 seconds]
xcombelle has quit [Ping timeout: 252 seconds]
attie has quit [Ping timeout: 252 seconds]
rjo has joined #m-labs
attie has joined #m-labs
sandeepkr_ has joined #m-labs
kuldeep has quit [Ping timeout: 240 seconds]
sandeepkr has quit [Ping timeout: 258 seconds]
kuldeep has joined #m-labs
sandeepkr__ has joined #m-labs
sandeepkr_ has quit [Ping timeout: 244 seconds]