Taylor Cramer
Taylor Cramer
Currently, there's no distinction between attributes and properties-- attributes are used as attributes in HTML and as properties in the browser. This is necessary for things like "value" to work--...
Equivalent to [Elm's map](http://package.elm-lang.org/packages/elm-lang/html/1.1.0/Html-App#map). I've been working on it in the mappable-listeners branch, but it's extremely messy and requires a bunch of extra traits. A much simpler solution would be...
Currently, `render` functions that include dynamically allocated types (primarily `Vec`s) need to re-allocate each time. It'd be nice to have some sort of pooling support. One possibility would be to...
This would save a bunch of unnecessary allocations, and it is entirely safe since the state can't be modified between `Renderer::render` being called and the `DomNode` being drawn to the...
For inspiration: https://guide.elm-lang.org/interop/javascript.html
Edit: A [draft RFC](https://github.com/cramertj/impl-trait-goals/blob/impl-trait-in-traits/0000-impl-trait-in-traits.md) for this feature was written. Linking here for visibility. This is really two separate but related features: `impl Trait` in trait definitions, and `impl Trait` in...
The ability to specify that an `impl Trait` return type only implements a trait if some other bound is met. ```rust trait Foo { fn foo(x: T) -> impl Debug...
Basically what the title says: ```rust const CONST_FOO: impl Trait = 11; static STATIC_FOO: impl trait = 27; let val_foo: impl Trait = 42; ```
The general goal of this issue is to be able to name an `impl Trait` type. @aturon sketched out [a strawman](https://github.com/rust-lang/rfcs/blob/master/text/1951-expand-impl-trait.md#appendix-a-sketch-of-a-fully-explicit-syntax) for this in their expanded `impl Trait` RFC. The...
Auto traits currently leak through `impl Trait`. It might be nice to provide a way to explicitly state that an `impl Trait` does not promise `Send` or `Sync` in order...