Another reason the second may be better: - Wrap the stack program in a transacti... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		Daniel_Newby on June 18, 2012 \| parent \| context \| favorite \| on: A Gray Beard Explores F# Another reason the second may be better: - Wrap the stack program in a transaction and simply discard the results to roll back the transaction. In an imperative program it is error prone to roll back a complicated operation—the most innocent looking function might mutate external state.

masklinn on June 18, 2012 [–]

Well technically F# has no purity handling, so it's just as possible for the most innocent-looking F# function to have side-effects as well.

Daniel_Newby on June 18, 2012 | [–]

Thanks for the warning. That sucks.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact