Can SpecializationData subsume TypeSpec?

[Shfty]

• i.e. Use int / float / double tags inside spec data instead of a type parameter, leave concrete data type to the implementation
• Would be much cleaner minus the type param
• How to deal with the need to store concrete data in Value?
  • Could use an int / float / double enum, but that seems restrictive
  • Enum with one variant per rust numeric type, leave conversion (and respecting of bittage etc) down to the implementation
  • May be best to use a single numeric type T, compose it in vector enums manually, and let downstream code handle conversion
• Abstraction is too coarse as-is; need to be able to explicitly specify integers for ex. loop index
  • Ergo, it comes down to an abstraction over precision
  • However, this is also too coarse, as Rust's int precision doesn't line up with its float precision
    • i.e. No f8, f16, f128
  • Solution is probably to split Number into Int and Float, defer precision to specialization
    • Tricky, since it's desirable to support integers for things like Distance, Position, Gradient
    • Perhaps the properties themselves will need to be able to specialize

[Shfty]

PARTIAL: Switched to enum-based uint / sint / float / number / vector representation covering rust's primitive types; properties are individually typed, and will panic if an invalid operation is attempted.