> Under the current regime this is not a breaking change because the authors do not intend `Point` to be serializable and do not want its consumers to serialize

> Under the current regime this is not a breaking change because the authors do not intend `Point` to be serializable and do not want its consumers to serialize it directly. If there's a central part of Rust that will prevent it becoming as ubiquitous as C, I believe its this philosophy. It's not just a focus on "safety" but this absolutist position on some idea of correctness, which may or may not even useful. Preventing programmers from doing things like, gosh, printing struct's because it might possibly somehow create a compile time issue. There's plenty of ways to let a programmer handle ambiguity issues, even on a per crate level, etc. Glad to see some folks are at least considering compile time reflection. Rust for me feels like an archaic language due to its weak compile time programming. It prevents many powerful safety constructs where a programmer can add compile time checks specific to a program domain.