Spoiler: they're nearly to the point (maybe now they've achieved it fully) of autogenerating a new language backend from ISA documentation PDFs! Bring that up next time someone complains about Go not using LLVM.
PeachPy, an x86-64 assembler in Python, is often used to target Golang assembler without dealing with its weird syntax. PeachPy uses Intel assembly syntax, but can generate assembly listing for Golang toolchain as its output. Damian Gryski wrote a tutorial about using PeachPy for Golang assembly: https://blog.gopheracademy.com/advent-2016/peachpy/
As that site indicates, in X.org with the defaults, '·' is easily typed with 'Compose . -', 'Compose . ^' or 'Compose ^ .' (this should also work from the console in Debian, at least, which uses xkb bindings throughout).
I love the Compose key, and don't think I'll ever use a desktop without it.
Excellent read about Go Assembly and how to use it. I'd love to see more on this, especially since assembly isn't something that often used, but after reading your post I can appreciate the overhead of having to maintain it in the future.
Thank you for the time put in the post about this.
If writing assembly code to run in the Go environment, and you're changing pointers, you have to write garbage-collector aware code.[1][2] Go has concurrent garbage collection, which means there are some unusual constraints on code that manipulates pointers.
This is an area where proofs of correctness are considered necessary, because intuition fails. See [3]
To be honest, the same issue happens on desktop browsers, it's just not as noticeable because the default zoom kinda matches what you'd expect. But you can still scroll to the side, in a desktop browser. See:
However, different browsers behave differently™, so you may need to also add:
word-wrap: break-word;
white-space: pre-wrap;
To make it work in Firefox (but you might need to adjust other things, also play with word-break CSS property, and test in all browsers). I've dealt with this previously at https://github.com/shurcooL/play/issues/4 and other places that deal with displaying user generated content.
In more general terms, take a look at Montgomery multiplication[1] which is where this trick originates. It's a common technique used by compilers to optimise away divisions.
Spoiler: they're nearly to the point (maybe now they've achieved it fully) of autogenerating a new language backend from ISA documentation PDFs! Bring that up next time someone complains about Go not using LLVM.