News for hackers. Stuff that matters.

A comment on A Python-to-JavaScript Transpiler with BabelJS and SourceMaps.

Re:A Python-to-JavaScript Transpiler with BabelJS and Source... by orf on Thursday March 31, 2016 @10:26AM (#11397385)
This is awesome! One comment, it might be a good idea to make the docstrings in JS appear above the functions rather than inside them? Chrome refuses to optimize functions if they are above a certain size in bytes, which includes comments, so it seems most 'docstrings' are placed above the definition rather than inside. Also does str(x) convert to x.toString(x)?

I'm going to use this in a project I have in mind :)

[ Parent | on HN ]
Re:A Python-to-JavaScript Transpiler with BabelJS and Source... by azazel75 on Thursday March 31, 2016 @10:44AM (#11397540)
Good :-)

Do you have any link for this chrome detail about optimization?

str(x) conversion is missing... i'll will implement it asap

[ Parent | on HN ]
Re:A Python-to-JavaScript Transpiler with BabelJS and Source... by grayrest on Thursday March 31, 2016 @01:32PM (#11398935)
It'd be related to inlining a function since size is a common rule there. Some searching turns up this[1] article on crankshaft from three years ago, which lists the restrictions as ">600 source characters including whitespace or 196 AST nodes".

[1] http://jayconrod.com/posts/54/a-tour-of-v8-crankshaft-the-op...

[ Parent | on HN ]