xdg-go / jibby Goto Github PK

To get a pretty syntax highlighting specify golang right after the opening triple backtick.

func main() {
   fmt.Println("Hello World!")
}

And very nice project, have to try it out.

Currently, the code switches on the length of an extended JSON key and then does a linear scan for key equality to dispatch. In most cases, the first letters are different (e.g. $code $date $type) and we could switch on the first letter after the $. That might be faster than chained if-else comparisons.

JSON RFC 8259 Section 7 describes rules for characters outside the BMP:

To escape an extended character that is not in the Basic Multilingual
Plane, the character is represented as a 12-character sequence,
encoding the UTF-16 surrogate pair. So, for example, a string
containing only the G clef character (U+1D11E) may be represented as
"\uD834\uDD1E".

This is not yet supported.