design: type system design #3
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "(deleted):main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In the new documents there my suggestions and ideas for a type system. not final or anything, just ideas.
@ -11,0 +38,4 @@
`[[(u8, u8, u8)]] * f32 -> [[(u8, u8, u8)]]`
Since all of the values are numbers (-> implementing `Num`/`Number`), they should be able to implicitely multiplied.
Typo.
@ -11,0 +20,4 @@
=== Generic-focused
Color-awareness may be handled as seperate types, so one might have `LinearRgb`, `SRgb`, `Xyz` etc. Optimally implemented using our own constructs.
Why not use the
palette
crate instead?I meant in-language constructs, but that's probably something to put on the far future todo list...
I'm concerned about lacking support for OCIO, but realistically, throw that on that list too lol
Can I change which branch I'm merging from? bc I fucked up and worked on main, resolved that locally now but this pr still tries to merge main
Yeah, after pushing the branch to your fork, you can use the
Edit
button at the top of this page to make the PR source and target configurable.I apparently can't switch the source :/
(pong)
Closing because I fucked up the git setup here and locally.
Pull request closed