Peter Atashian
Peter Atashian
Couldn't we just expand the channel for lightness to also use the full range of its integer type? Granted we wouldn't be following existing practice.
Perhaps we could have tag types for the 4 sizes of integers, with a trait + associated types specifying the signed and unsigned versions. Thus you can specialize the color...
Something like this ``` rust struct Int8; impl Something for Int8 { type Signed = i8; type Unsigned = u8; } struct ColorLab { L: T::Unsigned, a: T::Signed, b: T::Signed,...
There's now a bounty for this issue to incentivize someone to work on implementing this feature. https://www.bountysource.com/issues/70533351-tracking-issue-for-rfc-2627-link-kind-raw-dylib
Those "TBD files" are just the YAML equivalent of import libraries on Windows and are still separate files from the source code, so it isn't that novel.
> > > I have a question about one of the requirements in the RFC, in the second paragraph of the "Motivation" section. Specifically, which of the two options below...
Remember that `pc-windows-msvc` *also* requires the CRT to link against. There are bits of the CRT that *have* to be linked in statically (even when using the dll version of...
I do plan on adding km support, however I don't have the time to dedicate to investigating it fully at the moment.
PR needs to be updated to run on new CI.
Reviewing this PR is being postponed until winapi 0.3 is finally published, at which point I will investigate things like these.