Sergey Samokhov hoichi

Pragmatic Termination Analysis

We present a program analysis motivated by the need to solve some termination problems observed during the development of a parser for the new syntax introduced with the ReScript language. Learning from previous experience, it was decided to avoid parser generators, and go instead for a hand-crafted parser. In this way, the parser could be optimized for performance, be more maintainable, and most importantly give much more flexibility with error messages.

The new parser delivered on the promises, though a new issue appeared during live testing. The laptop would get hot once in a while, and only improve after re-starting the editor. Not all the time, but often enough to notice. The problem was an infinite loop in the parser, triggered by unexpected character combinations introduced while editing and never encountered in automated tests. It took a while to reproduce the issue and locate a mistake in the p

For getting webstorm fully install as a regular ubuntu app, and don't have to launch it with the script ./webstorm.sh add these webstorm.desktop in your /usr/share/applications/. Don't forget to replace WEBSTORM_PATH by your webstorm absolute path

[Desktop Entry]
Type=Application
Name=JetBrains WebStorm
Exec=WEBSTORM_PATH/bin/webstorm.sh %f

Icon=WEBSTORM_PATH/bin/webide.png

Essential JavaScript Links

I no longer mantain this list. There are lots of other very comprehensive JavaScript link lists out there. Please see those, instead (Google "awesome JavaScript" for a start).

	// Returns a function, that, as long as it continues to be invoked, will not
	// be triggered. The function will be called after it stops being called for
	// N milliseconds. If `immediate` is passed, trigger the function on the
	// leading edge, instead of the trailing.
	function debounce(func, wait, immediate) {
	var timeout;
	return function() {
	var context = this, args = arguments;
	var later = function() {
	timeout = null;