Stepan Koltsov

Modern allocators (like tcmalloc) are very efficient in allocating small objects, and Clay should probably have core library easy to maintain rather than highly optimized.

There's simpler solution: ``` record SmallInPlace ( data: Array[Byte, TypeSize(RawPointer)]], ); record LargeInHeap ( data: RawPointer, ); // not generic variant MemoryHolderSmallInPlaceLargeInHeap (SmallInPlace, LargeInHeap); allocateMemorySmallInPlaceLargeInHeap(T): MemoryHolderSmallInPlaceLargeInHeap = if (TypeSize(T)

Are you considering no type classes at all? For me two ways to express the same thing is confusing: programmer can choose both: ``` define Sequence?(S) = ... [S when...

@jckarter > Error resolution in that fashion isn't practical. For more complex predicates, how do you decide which nodes of the call graph to show? Probably in the most situations...

@jckarter About cyclic imports. Because of public imports, cycles can always be broken without affecting API. There's a trivial mechanical algorithm to break cycle. Suppose you have two modules: `aaa`...

In that case compiler message that explains that it is know issue, would help.

CodeJar modifies style attributes of existing HTML, so to replicate initial rendering, a part of CodeJar sources would need to be copied into client code. But as you say...

CodeJar also modifies style on initialization: [here](https://github.com/antonmedv/codejar/blob/ee57335d2ae2b6125081a61bfb8712f3a6c2727b/codejar.ts#L33-L37).

> I think a better and cleaner approach is to render a placeholder in serverside That's exactly what I would want. > highlight codes in clientside. We could also highlight...

> You want an additional flag that will merge generic methods and traits? Yes, an additional flag that will merge all instantiations all generic functions/methods together. E. g. * merge...