It is currently expected that UIs will figure out when to hide msg_history_show messages by themselves.

I think this is bad for two reasons:

• It makes UIs less similar, increasing the number of things to learn when going from one UI to another.
• It makes UIs different from the TUI, which offers a press ENTER prompt when the time to hide msg_history_show messages has come.

After [di

Platform

We have currently simple GitHub page, but we need to think about it's update with some better design.

Currently register looks like:

   private static <T> void register(Map<T, T> substitutions, T annotated, T original, T target) {
        if (annotated != null) {
            guarantee(!substitutions.containsKey(annotated) || substitutions.get(annotated) == original || substitutions.get(annotated) == target, "Already registered: %s", annotated);
            substitutions.put(annotated,

On Ubuntu 20.10 x64

sys/sanitize.sh
export ASAN_OPTIONS=detect_odr_violation=0
export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libasan.so.6

Then run tests. Memory leak everywhere.

In my mind one of the key things (besides visualization) Sourcetrail provides is a useful graph structure for source code that can be used for various types of analysis, without having to go through the pain of writing a clang analyzer yourself. However, since sourcetrail doesn't have plugins (#1076), writing your own analysis tools is a bit of work, and may not let you use other kinds of graph an

In our sister project I introduced the _mph literal for speeds OpenLoco/OpenLoco#736
I'm almost definitely the underlying units are the same in OpenRCT2. Therefore we should bring in the same changes. First add the string literal code. Then find all of the velocity literals in the vehicle code.

Its quite easy to do just convert the literal to hex so 393216 = `0x6000