Hacker News Reader

Comment by DanielBMarkham | Hacker News Reader

Got an email from Microsoft -- I discovered a new bug in their F# compiler that breaks my startup app. I'm the first to find this fairly significant bug. I should be so proud.

So now I'm deciding how best to hack up my code to get around the bug.

Can't say I'm very happy about where I am, but I'll get it fixed soon enough.

It's very cool being on the cutting edge, as long as you don't bleed too much!

View on HN

ooh... what bug? and are you doing f# for web or just f#?

I was going to blog about it tomorrow (never ruin a good chance to blog)

Basically for some reason F# barfs on large types, say types with 500 fields in them. I think the breaking point is 300 or so. There's also another bug that I'll save for the blog entry.

Microsoft was responsive as hell -- I had an email response within minutes and the engineer and I were emailing back and forth all afternoon. I was very impressed. The F# dev guys rock, even though I'm not happy at all with having a broken app.

yeah - that's been my experience too. the few times i've dealt with them, they've been back at me in hours tops. hopefully that'll continue despite them hitting RC

The odd thing was that the code was working in 2010Beta, but fell completely apart in 2010RC. It was a case of upgrading the IDE and having my app crash and burn. First thing we did was up the stack size, but no matter how big we made the stack, it didn't work.

interesting. well - we had the same problem with ndjango. worked fine with beta, crapped out with rc. that, and the shifty api is getting annoying. their last minute shift away from ocaml naming was pretty annoying.

That's because you are working on their bleeding edge software, if you are working on old platforms, usually they would just mark your bug report as "won't fix".

Reply on news.ycombinator.com