You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 23, 2018. It is now read-only.
In the context of a discussion on Class Morphing
adriaan said:
I'd envision something more lightweight (in the sense of adding fewer
new concepts to a scalac that already supports type-level computation,
which we all know to be inevitable). It would suffice for the compiler
to statically lift classes to their type level representation, and lower
type-level descriptions of classes to the corresponding actual class
(i.e., byte code)
The actual processing of these "data" (type) structures would use
general-purpose type-level computation (the type-level version of the
standard collection library's map, filter, etc), rather than a dedicated
language construct.
In short, generalise manifests to all declarations and definitions
and a lift them from the value level to the type level (since they're
statically known that should be realistic). Add type-level computation.
Stir well.