One thing that has been occurring to me on this is that it is probably reasonably practical to have a tool infer and update the contracts. The tool could limit itself to a restricted set of statements, without the spec needing to actually limit them directly.
On Wed, 5 Sep 2018 at 09:17 thwd <sedeveloper...@gmail.com> wrote: > If you can't use operations not explicitly stated in a contract: the more > reason to copy-paste a function body into a contract. > > What I mean by implicit constraints is what the draft calls "implied > constraints". > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
