As I’m implementing the type system I’m stepping all over this limitation.
At this point, the get-codec interface is sync in the browser and in Node.js so the async API surface of .encode() and .decode() is entirely future proofing.
The problem I’m having in the type system is that I need to get information out of the block in the constructor of several classes and I can’t do that because constructors aren’t async.
As I’m implementing the type system I’m stepping all over this limitation.
At this point, the
get-codec
interface is sync in the browser and in Node.js so the async API surface of.encode()
and.decode()
is entirely future proofing.The problem I’m having in the type system is that I need to get information out of the block in the constructor of several classes and I can’t do that because constructors aren’t async.
Any objections @vmx?