Why do we allow assignments to block args at all?

Could the time be ripe for disallowing Scanner allowBlockArgumentAssignment by default?

Best,
Christoph

________________________________
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von commits at source.squeak.org <commits at source.squeak.org>
Gesendet: Montag, 11. Mai 2020 03:23 Uhr
An: squeak-dev at lists.squeakfoundation.org; packages at lists.squeakfoundation.org
Betreff: [squeak-dev] The Trunk: Nebraska-tpr.57.mcz

tim Rowledge uploaded a new version of Nebraska to project The Trunk:
http://source.squeak.org/trunk/Nebraska-tpr.57.mcz

==================== Summary ====================

Name: Nebraska-tpr.57
Author: tpr
Time: 10 May 2020, 6:23:13.835738 pm
UUID: 52d8a16e-0096-4d51-a380-0fe4b0732434
Ancestors: Nebraska-mt.56

Correct a case of assigning to a block arg

=============== Diff against Nebraska-mt.56 ===============

Item was changed:
  ----- Method: NebraskaSenderMorph>>hideField: (in category 'as yet unclassified') -----
  hideField: aFieldName
+        fields at: aFieldName ifPresent: [:f| |m |
+                m := f.
-        fields at: aFieldName ifPresent: [:m |
                 [m owner notNil and: [m owner submorphs size =1]]
                         whileTrue: [m := m owner].
                 m delete]!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200516/93409594/attachment.html>