# How to reduce temporal update boilerplate for state-rich models?

**URL:** <https://alloytools.discourse.group/t/how-to-reduce-temporal-update-boilerplate-for-state-rich-models/219>\
**Category:** Questions\
**Created:** [January 21, 2022, 1:08am UTC](https://alloytools.discourse.group/t/how-to-reduce-temporal-update-boilerplate-for-state-rich-models/219 "2022-01-21T01:08:39Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![peter.kriens](https://yyz2.discourse-cdn.com/free1/user_avatar/alloytools.discourse.group/peter.kriens/32/3_2.png) [@peter.kriens](https://alloytools.discourse.group/u/peter.kriens)\
**Post date:** [January 24, 2022, 9:56am UTC](https://alloytools.discourse.group/t/how-to-reduce-temporal-update-boilerplate-for-state-rich-models/219/5 "2022-01-24T09:56:40Z")

</div>

A few years ago I made an attempt to support a Pluscal like language in Alloy. One of the features was that it traversed all the logical paths and automatically ensured the non-used variables were kept constant if not mentioned in a branch.

[PlusCal in Alloy](https://alloytools.discourse.group/t/pluscal-in-alloy/59)

It never generated a lot of interest so I stopped pursuing it. I made a deplorable joke that seemed to have upset some sensitive souls and that dominated the discussion 🙂 but reviving the part that keeps unused variables constant might be an idea.

I agree that doing it manually is very error prone and tedious.

---

_[View the full topic](https://alloytools.discourse.group/t/how-to-reduce-temporal-update-boilerplate-for-state-rich-models/219)._