4 commits

Author	SHA1	Message	Date
Brian Carroll	4aa2452e01	gen_wasm: Change some compiler bugs error handling from Result to panic ... Result makes sense where I have something meaningful to say to the user like "X is not implemented yet". And also for public functions that may interface with other parts of the project like Backend. But for private functions internal to gen_wasm, it's just unhelpful to get a stack trace to where the Result is unwrapped! I want a stack trace to the root cause. I always end up temporarily rewriting Err("oops") to panic!("oops") and then waiting for it to recompile. This feels like a more balanced approach, using each technique where it makes sense.	2021-10-02 13:40:44 +01:00
Brian Carroll	f1b14c14e3	Refactor SymbolStorage to emphasise stack/non-stack params ... We don't have much (any) code that cares about the difference between heap pointers and other primitives, but we have a _lot_ of code that cares if it's stack memory. So let's encode it that way.	2021-09-30 17:04:16 +01:00
Brian Carroll	7ea59ad9d4	PR tidy-ups	2021-09-29 06:15:58 +01:00
Brian Carroll	02bb9028ef	Returning records on the stack from Wasm dev backend!	2021-09-28 08:06:59 +01:00