630 unintentionally swapped the values for max_storage_pages and max_stack_size.
Losing semantic information was a bad idea, and constructor functions for structs with all fields public are non-beneficial. Functions with many arguments, also a bad idea.
This seemingly subtle change led to a stack overflow on an intel machine, but not on M1 Pro for some reason, worth investigating later. As it's part of why it wasn't caught earlier.
630 unintentionally swapped the values for
max_storage_pagesandmax_stack_size.Losing semantic information was a bad idea, and constructor functions for structs with all fields public are non-beneficial. Functions with many arguments, also a bad idea.
This seemingly subtle change led to a stack overflow on an intel machine, but not on M1 Pro for some reason, worth investigating later. As it's part of why it wasn't caught earlier.