1
Fork 0

fix typos

This commit is contained in:
Dante-Broggi 2019-08-17 15:33:44 -04:00
parent d65e272a9f
commit a7c34f1ce9
2 changed files with 2 additions and 2 deletions

View file

@ -306,7 +306,7 @@ impl<'tcx, Tag: Copy, Extra: AllocationExtra<Tag>> Allocation<Tag, Extra> {
/// ///
/// zsts can't be read out of two reasons: /// zsts can't be read out of two reasons:
/// * byteorder cannot work with zero element buffers /// * byteorder cannot work with zero element buffers
/// * in oder to obtain a `Pointer` we need to check for ZSTness anyway due to integer pointers /// * in order to obtain a `Pointer` we need to check for ZSTness anyway due to integer pointers
/// being valid for ZSTs /// being valid for ZSTs
/// ///
/// It is the caller's responsibility to check bounds and alignment beforehand. /// It is the caller's responsibility to check bounds and alignment beforehand.

View file

@ -297,7 +297,7 @@ impl<'mir, 'tcx, M: Machine<'mir, 'tcx>> Memory<'mir, 'tcx, M> {
/// and `align`. On success, returns `None` for zero-sized accesses (where /// and `align`. On success, returns `None` for zero-sized accesses (where
/// nothing else is left to do) and a `Pointer` to use for the actual access otherwise. /// nothing else is left to do) and a `Pointer` to use for the actual access otherwise.
/// Crucially, if the input is a `Pointer`, we will test it for liveness /// Crucially, if the input is a `Pointer`, we will test it for liveness
/// *even of* the size is 0. /// *even if* the size is 0.
/// ///
/// Everyone accessing memory based on a `Scalar` should use this method to get the /// Everyone accessing memory based on a `Scalar` should use this method to get the
/// `Pointer` they need. And even if you already have a `Pointer`, call this method /// `Pointer` they need. And even if you already have a `Pointer`, call this method