You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "context 0.1" file format has one model for a given field.
Say you have a file where someone's pasted two source files together and the first half of the file uses "var" and the second half uses "let" and "const." In context 0.1 you'll end up with a model with a mixture of var, let and const and need 1-2 bits for each symbol to describe variable kinds.
If instead the file format could have multiple models and switch between them, then for the first half of the file it could have a model specifying 0-bits for "var" and then a switch and a model with 1 bit for "let" or "const", and that would be good.
There are probably fancier ideas where you switch sets of related models at once.
Brotli does something like this, if you look at RFC7932 and the Block-Switch stuff.
The text was updated successfully, but these errors were encountered:
The "context 0.1" file format has one model for a given field.
Say you have a file where someone's pasted two source files together and the first half of the file uses "var" and the second half uses "let" and "const." In context 0.1 you'll end up with a model with a mixture of var, let and const and need 1-2 bits for each symbol to describe variable kinds.
If instead the file format could have multiple models and switch between them, then for the first half of the file it could have a model specifying 0-bits for "var" and then a switch and a model with 1 bit for "let" or "const", and that would be good.
There are probably fancier ideas where you switch sets of related models at once.
Brotli does something like this, if you look at RFC7932 and the Block-Switch stuff.
The text was updated successfully, but these errors were encountered: