ioreg: set-to-clear registers should still have getters

Author: bgamari

ioreg/builder/accessors.rs

@@ -67,7 +67,8 @@ fn build_field_accessors<'a>(cx: &'a ExtCtxt, path: &Vec<String>,
                             build_field_get_fn(cx, path, reg, field)),
     node::ReadOnly  => vec!(build_field_get_fn(cx, path, reg, field)),
     node::WriteOnly => vec!(build_field_set_fn(cx, path, reg, field)),
-    node::SetToClear => vec!(build_field_clear_fn(cx, path, reg, field)),
+    node::SetToClear => vec!(build_field_clear_fn(cx, path, reg, field),
+                             build_field_get_fn(cx, path, reg, field)),
   };
 
   let access_tag = match field.access {

ioreg/ioreg.rs

@@ -266,11 +266,12 @@ format!("txe={}, rxe={}, br={}", cr.txe(), cr.rxe(), cr.br())
 
 In the case of read-only (resp. write-only) fields the set (resp. get)
 method is omitted. In the case of `set_to_clear` fields a `clear`
-method is instead produced. For instance, in the case of the `sr`
-register's `fe` flag,
+method is instead produced in place of `set`. For instance, in the
+case of the `sr` register's `fe` flag,
 
 ```
-pub fn clear_fe(&self) -> UART_sr_Update { ... }
+pub fn fe(self: &UART_sr_Getter) -> bool { ... }
+pub fn clear_fe(self: &UART_sr_Update) -> UART_sr_Update { ... }
 ```
 
 ### Informal grammar