strager

@ybl3 Do you need any help with this task?

> Is this warning only for || conditions, or for all conditions with string literals? Good question. I think we should do just `||` for now. > Also, should I...

Thanks for reporting! There is a real bug which affects the main program as well.

Fixed in Git commit 02a1c8949b4fc1a897afa90dc871eda74d6f9764.

Fix released in [version 3.2.0](https://quick-lint-js.com/releases/#3.2.0).

> Are strings within the parser encoded in any specific format (UTF-8, UTF-16**) or does it need to be able to "catch-all"? Within quick-lint-js's parser, source code is in UTF-8....

We have a few options: 1. Status quo: Hand-write the format spec ([CTF][]) and hand-write parsers (JS, C++, and 010 Editor) and writers (C++). 2. Hand-write the format spec (CTF)....

I asked about option 2 in the LTTng mailing list: https://lists.lttng.org/pipermail/lttng-dev/2023-August/030593.html

In commit c0eeb811d15e986ffbc5f1da37adf6f73c7eef3a, I generated the CTF metadata file from using the C++ code (trace-types.h) as the schema. I'll do similar things to generate readers and writers soon.

JS parser generation implemented in commit 9581b8bfa42d9cd83dc3dd7feeb6d049980e0181.