about summary refs log tree commit diff
path: root/src/rustllvm/ExecutionEngineWrapper.cpp
diff options
context:
space:
mode:
authorManish Goregaokar <manishsmail@gmail.com>2015-03-19 06:08:43 +0530
committerManish Goregaokar <manishsmail@gmail.com>2015-03-19 08:24:36 +0530
commitc7392be96865c9e0717a73a4d4d4242d87232a5b (patch)
treeae5a43850d33303c0904863474a7940a02cae69f /src/rustllvm/ExecutionEngineWrapper.cpp
parent05354e852235c97d5231d71aeed75114fc55b59f (diff)
parenta51cd6116446d74a336abcb00f5ced3582ec307f (diff)
downloadrust-c7392be96865c9e0717a73a4d4d4242d87232a5b.tar.gz
rust-c7392be96865c9e0717a73a4d4d4242d87232a5b.zip
Rollup merge of #23468 - sfackler:stdio-panic, r=alexcrichton
 Nothing inside of the read/write interface itself can panic, so any
poison must have been the result of user code which the lock isn't
protecting.

This seems safe to me, but if we don't want to go this route we should update the docs to indicate that these methods can panic.

r? @alexcrichton
Diffstat (limited to 'src/rustllvm/ExecutionEngineWrapper.cpp')
0 files changed, 0 insertions, 0 deletions