Skip to content

Improve typing for CAN/CAN-FD frames #60

Description

@pd0wm

Try to make impossible states not representable, but hopefully not by making the UX worse. E.g.

  • Remote frames cannot contain any data. Separate type?
  • Remote frames cannot be CAN-FD.
  • Split out CAN/CAN-FD data frames into separate types? Or keep as a flag? CAN-FD has special flags (e.g. BRS).
  • Split out Error frame as separate type?
  • Investigate use of [u8; 64] instead of Vec for CAN data storage

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions