The JS++ core is now down to 9 low-priority bugs after 3.5 years of engineering and 400k+ lines of source code thanks to our lead engineer, Anton Rapetov.<\/p>\n
Building on top of our release of “existent types” to prevent out-of-bounds errors, we’ve had enough time for testing and feedback to discover that existent types work, and they will remain a cornerstone of JS++ going forward into the future.<\/p>\n
This latest release, version 0.9.1, focuses primarily on bug fixes. We value disciplined engineering, and we wanted to pay back technical debts. However, despite the bug fix theme, there are a few notable features and announcements. I’ll highlight what’s new or changed, and the list of bug fixes will be at the end.<\/p>\n
While we’ve had Console.log<\/a> for a long time, it doesn’t include critical information on where the log message originated from. You might find the new Console.trace<\/a> method more useful:<\/p>\n filename.js++:3:0: Now we have the original file location, line number, and column number for our logs!<\/p>\n We’ve also had block scoping semantics<\/a> for a long time. JS++ brings you high-performance block scoping — even in ECMAScript 3 environments.<\/p>\n In the latest version, block scoping is finalized and all corner cases should be covered. Specifically, we fixed code generation corner cases of lowering to the function scoping semantics of ECMAScript 3.<\/p>\n (We are keenly aware of the block scoping available in ECMAScript 3+ ‘catch’ blocks, which we addressed since the very first release of JS++ as being too costly in terms of performance. This is a gem of the ECMAScript specification that few people know about, and it highlights why you should trust our knowledge and experience – rather than choosing Microsoft just on brand name – going into the future.)<\/p>\n In the last version, 0.9.0, we announced existent types to prevent runtime out-of-bounds errors. In this release (0.9.1), we are doubling down on existent types and revising the rules based on experience, feedback, and re-design:<\/p>\n In previous releases, we had left nested generics (with generic parameters) unimplemented. Previously, the following code worked:<\/p>\n The latest version now enables nested generics with generic parameters:<\/p>\n Finally, here is a list of all the other bug fixes. There are a lot. The latest 0.9.1 release brings JS++ software quality to its highest level yet by addressing technical debt rather than delivering new features.<\/p>\n Fixed:<\/p>\n Software quality at JS++ has always remained high, and that’s a testament to the ability of our lead engineer, Anton Rapetov, and our engineering approach. In more than 3.5 years of engineering, we currently have fewer than 10 open bug reports in the core compiler.<\/p>\n","protected":false},"excerpt":{"rendered":" The JS++ core is now down to 9 low-priority bugs after 3.5 years of engineering and 400k+ lines of source code thanks to our lead engineer, Anton Rapetov. Building on top of our release of “existent types” to prevent out-of-bounds errors, we’ve had enough time for testing and feedback to discover that existent types work, … Continue reading “JS++ 0.9.1: Bug Fixes”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[2,4],"tags":[],"_links":{"self":[{"href":"https:\/\/www.onux.com\/jspp\/blog\/wp-json\/wp\/v2\/posts\/995"}],"collection":[{"href":"https:\/\/www.onux.com\/jspp\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.onux.com\/jspp\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.onux.com\/jspp\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.onux.com\/jspp\/blog\/wp-json\/wp\/v2\/comments?post=995"}],"version-history":[{"count":25,"href":"https:\/\/www.onux.com\/jspp\/blog\/wp-json\/wp\/v2\/posts\/995\/revisions"}],"predecessor-version":[{"id":1021,"href":"https:\/\/www.onux.com\/jspp\/blog\/wp-json\/wp\/v2\/posts\/995\/revisions\/1021"}],"wp:attachment":[{"href":"https:\/\/www.onux.com\/jspp\/blog\/wp-json\/wp\/v2\/media?parent=995"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.onux.com\/jspp\/blog\/wp-json\/wp\/v2\/categories?post=995"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.onux.com\/jspp\/blog\/wp-json\/wp\/v2\/tags?post=995"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Block Scoping<\/h3>\n
Existent Types<\/h3>\n
\n
T<\/code> has an implicit conversion to external<\/code>, T+<\/code> also has an implicit conversion to external<\/code><\/li>\n??<\/code>) has a higher operator precedence. See the operator precedence<\/a> documentation.<\/li>\nvoid+<\/code> and any usages of void<\/code> except as a return type<\/li>\nexternal<\/code> as a common type for int<\/code> and string<\/code> for the safe navigation operator (??<\/code>). Thanks to user @h-h in the JS++ Community Chat<\/a> for reporting this bug.<\/li>\nNested Generics with Generic Parameters<\/h3>\n
\r\nArray<Array<int>> arr1; \/\/ nested, non-parametric\r\nArray<T> arr2; \/\/ non-nested, parametric\r\n<\/pre>\n
\r\nArray<Array<T>> foo; \/\/ nested *and* parametric\r\n<\/pre>\n
Bug Fixes<\/h3>\n
\n
super()<\/code> on base class<\/li>\nnew<\/code><\/li>\nConclusion<\/h3>\n