aboutsummaryrefslogtreecommitdiff
path: root/src/stage1/parser.cpp
diff options
context:
space:
mode:
authorFrank Denis <124872+jedisct1@users.noreply.github.com>2021-04-20 19:57:27 +0200
committerGitHub <noreply@github.com>2021-04-20 19:57:27 +0200
commit10f2d6278946485f057f65bbb3c094a6fcde1adf (patch)
treed7e4f5182e5fd226a705fb3bfbab9d35faa1e1ef /src/stage1/parser.cpp
parent1e06a74348d11e4eef456a067dc5065c1e8b1ee9 (diff)
downloadzig-10f2d6278946485f057f65bbb3c094a6fcde1adf.tar.gz
zig-10f2d6278946485f057f65bbb3c094a6fcde1adf.zip
std/crypto: use finer-grained error sets in function signatures (#8558)
std/crypto: use finer-grained error sets in function signatures Returning the `crypto.Error` error set for all crypto operations was very convenient to ensure that errors were used consistently, and to avoid having multiple error names for the same thing. The flipside is that callers were forced to always handle all possible errors, even those that could never be returned by a function. This PR makes all functions return union sets of the actual errors they can return. The error sets themselves are all limited to a single error. Larger sets are useful for platform-specific APIs, but we don't have any of these in `std/crypto`, and I couldn't find any meaningful way to build larger sets.
Diffstat (limited to 'src/stage1/parser.cpp')
0 files changed, 0 insertions, 0 deletions