I'm interested in machine learning, functional programming, compilers and computational biology.

Aug
27
awarded Supporter
Aug
26
comment Python - Create a list with initial capacity
As @Philip points out the conclusion here is misleading. Preallocation doesn't matter here because the string formatting operation is expensive. I tested with a cheap operation in the loop and found preallocating is almost twice as fast.
Aug
23
awarded Notable Question
Aug
11
comment Crypto hash in 'a href'?
argh, this was almost perfect. It looks like support for the anchor tag was initially a part of the spec but was removed, at least for the 1.0 version: github.com/w3c/webappsec/issues/81 . Oh well...
Aug
11
awarded Scholar
Aug
11
comment Crypto hash in 'a href'?
This is perfect! Thanks for the pointer. BTW for anyone reading this post qnimate.com/… explains how to use sub resource integrity with an 'a' tag.
Aug
11
accepted Crypto hash in 'a href'?
Jul
24
awarded Nice Answer
Jun
8
comment Crypto hash in 'a href'?
For what I'm proposing the referring site gets to set the hash for the site that it references. That is a critically important part of the use case and I don't think that is the case with ssl/https... right? I also don't understand why you say 3) isn't addressed. It's just adding a hash that's normally given as text for the user to validate in an attribute and asking the browser to validate. Sorry if I'm just being slow here.
Jun
8
comment Crypto hash in 'a href'?
Thanks, I'm aware that 1) and 2) are not valid use cases but I do think that 3) is actually a pretty big deal. I often download binaries from sites that use mirrors for download. They usually provide hashes but I very rarely check them even though I know I should... I'm guessing I'm not the only one in this boat.
Jun
8
awarded Student
Jun
8
asked Crypto hash in 'a href'?
May
4
awarded Autobiographer
Apr
14
awarded Caucus
Jan
18
awarded Nice Question
Nov
28
awarded Autobiographer
Nov
28
awarded Supporter
Nov
23
comment stack overflow in F# compiler running under mono
in case anyone is following this here is the bug report bugzilla.xamarin.com/show_bug.cgi?id=24752
Nov
21
comment stack overflow in F# compiler running under mono
Thank you for the pointers and the work around. Turning off signature file generation is a fine workaround for me especially since I can just use the signature output from the windows build. I'll add a bug report to mono as you suggest when I get a bit of time.
Nov
21
accepted stack overflow in F# compiler running under mono
1 2 3 4 5