Re: [PATCH] * etc/NEWS: Document incompatibilities introduced by record types.

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > Since we agree that defining these symbols as record types should not
  > > be done, let's make it easier for programmers to avoid doing that.

  > I won't get in the way of someone else doing that, *as long as* it's
  > done via compilation-time (or even load-time) checks rather than
  > run-time checks (i.e. not in make-record).

We should do what is necessary to solve the problem.  Let's see what
is needed to prevent the problem.

The issue at hand is that defining a record called 'hashtable' or 'integer'
can alter how built-in types print.  That is a pitfall and we should put a
fence around it.

What are the concrete actions that would have this result?

Would using 'hashtable' or 'integer' in make-record cause that to occur?

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.