reified

They capture calls and turn them into reified values that can then be manipulated and queried.

The nice thing about the latter is that every action gets reified into a concrete value, on which we can perform any kind of computation we like.

The call for reified types in Java has been heard for over a decade now.

So if the platform had offered reified generics, Scala could still had chosen to ignore those and gone with type erasure.

Scala wouldn't even be possible in its current form if Java had used reified generics.

Individual laws are reified as commits, and the repository tracks the evolution of the code as laws get voted in and applied.

In Scheme, for example, a solution would be likely to involve delimited reified continuations and not need much in the way of macros.

C# or Rust are better in this regard, which both have reified generics.

I'd say they are vaguely related through decoupling the traditional structure of computations through reified objects.

Exactly the same argument can be applied to reified ('monadic') IO.

I occasionally take advantage of reified generics and reflections, but that is a different thing.

The rush many initially experience when exposed to the fact that their thoughts can be reified as programs which dutifully encode their wishes is quite intoxicating.

Specific to programming, when something is reified, it roughly means you can treat it as data (or "First-class object").

The word "reified pixel" is only being used by you so if you want to talk about it you need to define what that means.

In C# it is valid to do "T foo = new T();" and because of reified generics, this works.

Unless you have continuations/a reified control stack or program in a monadic style (which would essentially be CPS in this case), you cannot "fake" exceptions.

Reified pixels can be described in finite terms, and can be counted.

Reified generics allows the compiler to generate verify the code at compile time but generate actual optimized (with respect to the type) code when JITting.