Eldred Habert

The different output layout should be covered by #524, and z80 support by `.setcpu none` (but I don't know if we have an issue tracking that)

My vote goes to “no”. I'd rather improve the macro system so that macro packs can be written more conveniently, but not upstream support for a multi-system assembler. It's fine...

A macro pack can afford to be more opinionated than the upstream distribution, because it can simply cater to its implementer's preferences; and if another user prefers another set of...

I believe that MBC3 has a limit of 4 banks, but the JP Crystal-exclusive MBC30 has double. We should only talk about the format, and mention MBC30's differences in a...

Here's how I envision this: - A fragment whose priority is not specified defaults to 0. - Priorities are *signed*. - Ties are broken using link order (backwards compat, determinism)....

A major difference is that fragments and their priorities are spread across multiple files, which begets mixups if used without a centralised definition.

It does contain some useful info nonetheless, which is why I believe we've been reluctant to outright delete it thus far. If #379 could be driven to completion, then this...

I don't like this, because it solidifies a lot of internal details, it has a high maintenance cost, and it's too general. This would be one huge grammar rule in...

Does either https://gbdev.io/gb-opcodes/optables/ or https://rgbds.gbdev.io/docs/gbz80.7 fit what you have in mind?

The original table was very cryptic and not really accessible due to lacking descriptions; it also grouped instructions in weird ways. Can you draft up what info you'd like to...