From c7e2c21bb26d9f6610e8c0d39ad0f1710582ef4f Mon Sep 17 00:00:00 2001 From: Chris Fallin Date: Fri, 29 Apr 2022 10:35:03 -0700 Subject: [PATCH] ISLE language reference: move subsection to proper section. (#4087) In #4072 I mistakenly put the subsection about if-let clauses in the language doc just below the next section header, so it's in the wrong section ("mapping to Rust"). This moves it back upward to where it should be. Sorry about that! --- cranelift/isle/docs/language-reference.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/cranelift/isle/docs/language-reference.md b/cranelift/isle/docs/language-reference.md index bb6e7c0b86..a283136a4c 100644 --- a/cranelift/isle/docs/language-reference.md +++ b/cranelift/isle/docs/language-reference.md @@ -941,14 +941,6 @@ A term can have: 4. A single external constructor binding (see next section). -## ISLE to Rust - -Now that we have described the core ISLE language, we will document -how it interacts with Rust code. We consider these interactions to be -semantically as important as the core language: they are not -implementation details, but rather, a well-defined interface by which -ISLE can interface with the outside world (an "FFI" of sorts). - ### If-Let Clauses As an extension to the basic left-hand-side / right-hand-side rule @@ -1061,6 +1053,14 @@ following shorthand notation using `if` instead: (isa_special_inst ...)) ``` +## ISLE to Rust + +Now that we have described the core ISLE language, we will document +how it interacts with Rust code. We consider these interactions to be +semantically as important as the core language: they are not +implementation details, but rather, a well-defined interface by which +ISLE can interface with the outside world (an "FFI" of sorts). + ### Mapping to Rust: Constructors, Functions, and Control Flow ISLE was designed to have a simple, easy-to-understand mapping from