Chayim Refael Friedman
Chayim Refael Friedman
If you don't want extra fat pointers, don't use multiple traits. This is exactly the concept of "zero-cost abstraction".
> Should we allow `m!b"abc"` and `m!b'x'`? (I think yes.) A counterargument: `b""` is, to some extent, custom literal too - so its seems a little strange to allow `m!b""`...
I believe the solution is to disallow implementing `Fn*` multiple times, not introducing a new wrapper struct.
It will be at least easier with `const` blocks.
> I don't understand the issue; what's wrong with simply dereferencing the array? > > ```rust > match header.id { > BoxType::Id(BoxId(*b"mvhd")) => self.mvhd = Some(MvhdBox::read(header, reader).await?), > BoxType::Id(BoxId(*b"mvex")) =>...
Omit the `as wasm`: ```js import { Universe } from "wasm-game-of-life"; ```
Thanks @Thraka . However we need to move to using Microsoft.Xaml.Behaviors.Wpf. See [Open Sourcing XAML Behaviors for WPF](https://devblogs.microsoft.com/dotnet/open-sourcing-xaml-behaviors-for-wpf/). Or at least specifying System.Windows.Interactivity as a dependency.
:smile: Nice. As fire as I understood version 1 (beta) uses Microsoft.Xaml.Behaviors.
There's a concept of slaves in the Tora and changing the term to be politically correct is a postmodern thing that _Gedoilei Israel_ classify as trying to modernize the Torah...
How can we retrive the variable names from tuples? It may be easy in the case of call with immediate destructurings, but not so in the general case.