From 0393d101b1ede19a087f51fcd3111be1782384ce Mon Sep 17 00:00:00 2001 From: Y-Nak Date: Fri, 15 May 2020 23:47:16 +0900 Subject: [PATCH] Fix typo in peepmatic (#1712) --- cranelift/peepmatic/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cranelift/peepmatic/README.md b/cranelift/peepmatic/README.md index 550f6d310d..0d146ef520 100644 --- a/cranelift/peepmatic/README.md +++ b/cranelift/peepmatic/README.md @@ -321,7 +321,7 @@ optimizations. We walk the AST and gather type constraints. Every constraint is associated with a span in the source file. We hand these constraints off to Z3. In the case that there are type errors (i.e. Z3 returns `unsat`), we get the constraints that are -in conflict with each othe via `z3::Solver::get_unsat_core` and report the type +in conflict with each other via `z3::Solver::get_unsat_core` and report the type errors to the user, with the source context, thanks to the constraints' associated spans.