Shane F. Carr
Shane F. Carr
More paper trail: https://github.com/tc39/proposal-temporal/issues/11 followed by https://github.com/tc39/proposal-temporal/issues/33 followed by https://github.com/tc39/proposal-temporal/issues/707
> My priority then was avoiding the disaster of naming the zoneless type DateTime. This is my main potential worry with DateTimeFormatter; it looks like thing thing people should use...
- @echeran - jodatime is an arithmetic library. In that sense, an instant / zoned datetime makes sense. But for ICU4X, we're a formatting library, and we allow you to...
- @younies - How the Bi-di algorithm works is that no matter the encoding, it gives levels to chunks. So the algorithm seems easy to update. - @Manishearth - The...
@gregtatum will provide mentorship.
This isn't true. We already have `pub const fn RawBytesULE::from_array(arr: [u16; N]) -> [Self; N]` https://unicode-org.github.io/icu4x-docs/doc/zerovec/ule/struct.RawBytesULE.html#method.from_array It doesn't use `map`. It just uses plain index operations, which work in `const`.
> I'd prefer we don't do this: it's impossible to do until `[T; N]::map()` is stable const; and once that method is stable my recommendation would be to just use...
Related: https://github.com/unicode-org/icu4x/issues/1935
@Manishearth What is the size for this issue? If it is small, we could do it in 1.0, but if it's nontrivial, we should sit on it.
OK, let's put it in 1.1 then. Is this a good first/second issue?