Harry Pierson

> To me unified representation is easier to work with. #151 is more compact here, I agree, but it requires additional handling. When we first built the debugger, I was...

@roman-khimov Any progress on including the type system info from #151 into this NEP?

> I'm waiting for more feedback on "things intentionally omitted for now" and other general topics, "Address" (as a representation hint for Hash160) can be added as well if it's...

Neo Debug Info v2 uses a single string like @igormcoelho asked about. But I agree with @roman-khimov that a mechanism that is easier to parse is probably easier to get...

I'm back from vacation. Can we start making progress on this?

Info on .NET support in Unity: https://docs.unity3d.com/Manual/overview-of-dot-net-in-unity.html As per that doc, Unity recommends targeting .NET Standard 2.1. It appears there are additional limitations that stem from Unity execution environment (Mono...

This appears related to #1865, where the refactored domain assembly (which I call "nucleus" but I am in no way married to that term) is unity compatible. @Liaojinghui proposed #2547,...

~This was closed by #499~ Ignore this comment.

> @devhawk by https://github.com/neo-project/neo/pull/499? I'm sorry, this issue should *NOT* be closed. https://github.com/neo-project/neo-vm/pull/499 was the first step towards unity compatibility. But there are two additional steps needed: * Break Neo.dll...

Modified versions of `transaction_test1` from plv8 test suite Returns `error: procedure returned null record` when called: ```sql CREATE PROCEDURE transaction_test1(inout o text) LANGUAGE plv8 AS $$ for (let i =...