| commit | 069efdcf4037b7fa25586648bf733777cb6a453b | |
| author | malc <moosotc@gmail.com> | |
| Tue, 12 Jul 2016 23:58:42 +0000 (13 02:58 +0300) | ||
| committer | malc <moosotc@gmail.com> | |
| Tue, 12 Jul 2016 23:58:42 +0000 (13 02:58 +0300) | ||
| tree | 109f07d4e4aebbb80209bd9ab234076607b017cd | treesnapshot (tar.gz zip) |
| parent | 755587b164099ed4a81952c3812a2f9419c7a71d | commitdiff |
Give ml_postprocess a chance to succeed
Admittedly this is fugly, but no clean solution immediately springs to
mind.
(Register continuation that will be called upon unlock and will notify
caml code to retry? Use cloned contexts? Something else?)
All other trylocks are just as ugly, but probably much less noticeable.
Admittedly this is fugly, but no clean solution immediately springs to
mind.
(Register continuation that will be called upon unlock and will notify
caml code to retry? Use cloned contexts? Something else?)
All other trylocks are just as ugly, but probably much less noticeable.
| link.c | diffblobblamehistory |