port

RustScan has an accessible mode, rustscan --accessible which should promise not to have any weird ASCII text in it.

Write CI that runs RustScan with --accessible a few times, with different flags / options and check the terminal output to see if it contains one of these:

1. [!]
2. [~]
3. [>]
4. | {}

If any of these characters appear in any of the tests, fail the CI. E

When using ImGui.dragInt3 like so for example:

int[] TestArray = new int[3];
ImGui.dragInt3("Test", TestArray);

The result is identical to a dragInt2, there are only 2 boxes available.

The method WordList.QuerySuggest.Phonet has two nested loops that query for entries from a PhoneTable that have rules starting with a given character. Indexing these entries in the table by the first rule character may have a positive impact on performance.

• Test on ubuntu 18/19
• Test on other distributions
  • Debian
  • Mint
  • ...
• Track new found issues in this tracker