-
Notifications
You must be signed in to change notification settings - Fork 81
AssemblyScript conflicts #43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thank @MaxGraey for your help here :-) It's really appreciated! |
@MaxGraey There is still an error if a class variable is based on a constructor variable:
I had to change this: readonly progBytes : Uint8Array = Uint8Array.wrap(this.progMem.buffer);
constructor(public progMem: Uint16Array, private sramBytes: u64 = 8192) {
this.reset();
} To that: readonly progBytes : Uint8Array;
constructor(public progMem: Uint16Array, private sramBytes: u64 = 8192) {
this.progBytes = Uint8Array.wrap(this.progMem.buffer);
this.reset();
} |
Could you create minimal example on WebAssembly Studio? |
Without code I can't tell what's wrong. Plz open issue with minimal reproducible example |
Yes, I will open an issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue collects conflicts of the current code base and AssemblyScript. See #35 and the research project.
Found problems:
types
file can be adapted to keep JS compatibilityICPU
andCPU
. (further research required)CPU
withprogMem
, which has to be declared outside the constructor and the following instantiations have to be done in the constructor body:(The research is still ongoing.)
The text was updated successfully, but these errors were encountered: