nickchapman-da 44d0128f29 Add control to speedy compiler to choose if stack-trace support occurs at runtime. (#6070) ... Choices for `stacktracing` are `NoStackTrace` / `FullStackTrace`. Adapt code so the selection is made by the original caller: - `engine` - `scenario-service` - `repl-service` - `daml-script` runner etc Currently, all callers pass `FullStackTrace` (the existing behaviour), except for the exploration dev-code: `daml-lf/interpreter/perf/src/main/scala/com/daml/lf/explore`. The idea is that once this control is in place, we can discuss if we can change how we might expose it to the user, and/or perhaps change the default behaviour to have `stacktracing` disabled. changelog_begin changelog_end		2020-05-22 16:36:03 +01:00
..
client	Make max-inbound-message-size in DAML script/repl configurable (#5996)	2020-05-15 07:22:05 -04:00
protos	Split up repl tests to make them faster (#5450)	2020-04-07 10:22:15 +02:00
server	Add control to speedy compiler to choose if stack-trace support occurs at runtime. (#6070)	2020-05-22 16:36:03 +01:00