[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Why the inversion of mutability between make-rtd and define-record-type?
This page is part of the web mail archives of SRFI 99 from before July 7th, 2015. The new archives for SRFI 99 contain all messages, not just those from before July 7th, 2015.
- To: srfi-99@xxxxxxxxxxxxxxxxx
- Subject: Why the inversion of mutability between make-rtd and define-record-type?
- From: Derick Eddington <derick.eddington@xxxxxxxxx>
- Date: Sun, 10 Aug 2008 23:30:47 -0700
- Delivered-to: srfi-99@xxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=Fz3MBms36OxceUXJ8A5NavMThyPmq02tMYEgFTCIJoQ=; b=EggRR+qf9rBbMGzTHggGSdKlrPn6ppE+kAvI2Yzf5xIaJu46YF9QeUuH8hXIG01UgA LO4TxvQDuiV+3gK4Bf8sT456/UhQlSouKcJxadd4o5FOM2Qp82QExfrvK7gBVkrf3M3N br/6WOnr4OMj4C6g3JG7TykaGEzyi5XbZqYGU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=JBzXiuKPZDqRuFkRIAULA/dogDJTZnkVQNclmtK5W7Eppkl52VGXYiQSKioSHhoS2T /0ay0vGF6JanOEgqK5tzE/9X3u+MNGVxE5TuUccwF2Dudx+G6gMWFpblO8rZitc9kzPc exQE7Dv0uoRBO6nffIKxRD7MkUFzomEh3ZTAU=
What is the rationale for making make-rtd's succinct identifier-only
field spec mean mutability for the field instead of immutability? This
is a confusing mismatch with define-record-type's succinct
identifier-only field spec which means immutability. Also, I prefer the
philosophy of immutability by default and requiring more effort/thought
for mutability. Also, why is a succinct field spec even justified for
the procedural layer?
--
: Derick
----------------------------------------------------------------