News for hackers. Stuff that matters.
Re:Everyday hassles in Go by zzzcpan on Tuesday December 30, 2014 @10:27AM (#8814929)
Refcounting and a single threaded runtime, instead of GC and a multithreaded one.

By compiled regexpes, I meant replacing things like bytes.Equal(foo, "qwe") with things like foo.m(`^qwe$`) or even foo.m/^qwe$/ that have the same performance. All the loops that scan through slices could benefit from it, golang has a lot of them. Plus more overall matching/scanning consistency, that should lead to fewer mistakes.

Re:Everyday hassles in Go by vardump on Tuesday December 30, 2014 @11:00AM (#8815076)
Well, if you're happy to run them only over byte arrays, then you should be able to use PCRE and satisfy your performance requirements. Your regular expressions will get compiled into native code at runtime.

http://sljit.sourceforge.net/pcre.html

Re:Everyday hassles in Go by theseoafs on Tuesday December 30, 2014 @01:32PM (#8815897)
Go would need to be completely rearchitected in order to move to a single-threaded runtime.
Re:Everyday hassles in Go by im_dario on Wednesday December 31, 2014 @05:49AM (#8818887)
As far as I know, it should be enough with runtime.GOMAXPROCS(1) to run as single-threaded.
Re:Everyday hassles in Go by yepguy on Wednesday December 31, 2014 @03:21PM (#8820918)
No, the runtime will still create new threads whenever you call a C function or syscall.