Timeline for What are the use cases for different scoping constructs?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 4, 2022 at 20:39 | comment | added | userrandrand | It seems that InheritedBlock has been made a resource function with some added error messages since 2019 (after this answer was made). The possible issues section might also be interested to look at. The function is here | |
| Apr 20, 2015 at 14:27 | comment | added | WReach | @episanty The brackets are not strictly necessary but, following common convention, their presence gives the reader a clue that f is a potentially non-determinstic computation rather than a simple value. | |
| Apr 20, 2015 at 11:55 | comment | added | Emilio Pisanty | Are the brackets on f necessary? You could do the same with y:=x. | |
| Aug 8, 2012 at 13:36 | comment | added | WReach | @Reb.Cabin Trace will reveal the "implementation coincidence" that these expressions invoke RuleCondition in a manner useful to this context. See also the brief discussion here. | |
| Aug 8, 2012 at 13:02 | comment | added | Reb.Cabin | The last bit, forcing evaluation on the rhs of a rule, is interesting. There isn't much wiggle room, if any. The condition must be inside the block expression, not outside, so the documentation of Condition is little help understanding the trick. It must be RuleDelayed and not Rule, which is a bit easier to understand; you want the trick evaluated after substitution, not before. So it looks like you're getting a RuleDelayed that's going to eval a Condition; the Block incidentally forces one more round of evaluation before the test of the Condition -- something along these lines. | |
| Jan 24, 2012 at 20:29 | history | answered | WReach | CC BY-SA 3.0 |