"bits" is a valid field name

[japaric]

In that case the method to access the bitfield proxy:

peripheral.register.read().bits() // BitsR
peripheral.register.read().bits().is_variant() // bool

is ambiguous with the register method to get its raw bits

peripheral.register.read().bits()  // e.g. u8

This happens in the SKEAZN84.svd file.

[japaric]

Solution

Rename R.bits to something else. The question is what should be the new name. In principle any name we pick can cause a collision in the future as register names, per the SVD specification, are as, or more, free-from than Rust identifiers.

From the schema (register names have type dimableIdentifierType):

  <xs:simpleType name="dimableIdentifierType">
    <xs:restriction base="xs:string">
      <xs:pattern value="((%s)|(%s)[_A-Za-z]{1}[_A-Za-z0-9]*)|([_A-Za-z]{1}[_A-Za-z0-9]*(\[%s\])?)|([_A-Za-z]{1}[_A-Za-z0-9]*(%s)?[_A-Za-z0-9]*)"/>
    </xs:restriction>
  </xs:simpleType>

[zargony]

Also happened to me with ATSAM3X8E.svd. My workaround was to rename the field rather than the method (which works, but also feels wrong)

[japaric]

We can use [@whitequark's idea]](#99 (comment)) of renaming the 'bits` variant (when the enumeratedValue is named BITS) iff it would cause a collision with R.bits.