diff options
author | Dominik Picheta <dominikpicheta@gmail.com> | 2017-03-27 21:11:48 +0200 |
---|---|---|
committer | Dominik Picheta <dominikpicheta@gmail.com> | 2017-03-27 21:11:48 +0200 |
commit | e0bb65e45c8dec9683740f1a656f72f7eaa4d32f (patch) | |
tree | 415dcf608e39f250d6d35c0a2997d18d5dd5ff52 /compiler | |
parent | 159643824b4307597ece03597a44579c5fbcc9ed (diff) | |
download | Nim-e0bb65e45c8dec9683740f1a656f72f7eaa4d32f.tar.gz |
Fixes the order in which FutureVar and return completions are made.
This caused a pretty bad and subtle bug in the asynchttpserver. As far as I can understand, the fact that the returned future was being completed first meant that the underlying async procedure could continue running and thus clean() the FutureVar and request new data. The control then went back and the FutureVar was completed again causing an error.
Diffstat (limited to 'compiler')
0 files changed, 0 insertions, 0 deletions