srrrse

I think at very least lifetime elisions of references in statics is a good idea. It feels very silly to write `static FOOBAR: &'static str = "localhost:8080/foo"` with the word...

(NOT A CONTRIBUTION) > A local waker can be accessed with the local_waker method on Context and woken just like a regular waker. All contexts will return a valid local_waker,...

(NOT A CONTRIBUTION) possibly LocalWaker could also just be defined as `struct LocalWaker(Waker)` and you could store the waker as a `LocalWaker` in `Context`. Would be a bit counterintuitive but...

(NOT A CONTRIBUTION) > You're saying you doubt it would be possible to make this a monomorphization error? > > Just to be clear, you're not proposing to make Waker...

(NOT A CONTRIBUTION) > I was just thinking that if someone is trying to enhance performance by using local wakers, knowing if you actually got a local waker or if...

(NOT A CONTRIBUTION) @rust-lang/libs-api What is needed to make progress on this proposal? It seems like it has been dropped. You made the breaking change to support it last year...

(NOT A CONTRIBUTION) > I can imagine this. For example, tokio may want to add a local waker to access a Cell instead of a Mutex when waking a task....

Hey, I don't know a lot about this API, but I noticed that `StrSearcher` is not a double ended pattern, but `CharSliceSearcher` is. Is this an error? The explanation of...

@bluss That makes sense. The semantics of `CharSliceSearcher` are not documented; I assumed the char slice was treated as an ordered sequence rather than a set.

I strongly prefer the `struct` syntax, as in: ```rust trait Foo { struct { bar: u32, baz: u64, } } ``` For several reasons: * The clean separation of data...