@evref-bl/pharo-mcp 3.1.0 → 3.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/templates/pharo-references/pharo-coding.md +5 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@evref-bl/pharo-mcp",
3
- "version": "3.1.0",
3
+ "version": "3.2.0",
4
4
  "description": "Pharo MCP agent-host templates",
5
5
  "license": "MIT",
6
6
  "type": "module",
package/templates/pharo-references/pharo-coding.md CHANGED
@@ -58,11 +58,11 @@ allocates something nobody asked for. Pharo's fused messages exist for that:
58
58
  than a filtered copy to iterate over, `String streamContents:` rather than a
59
59
  chain of `,`, where every comma copies everything to its left.
60
60
 
61
- Sorting is the usual case. `sorted` and `sorted:` answer a sorted copy as an
62
- Array; `sort` and `sort:` sort a `SequenceableCollection` in place and answer
63
- it. So `values sorted` says what `values asSortedCollection asArray` says, with
64
- no `SortedCollection` in between. One earns its keep when a collection must
65
- *stay* sorted as things are added to it — not for sorting something once.
61
+ Sorting is the usual case. `sort` and `sort:` sort a `SequenceableCollection`
62
+ in place; `sorted` and `sorted:` leave the receiver alone and answer a sorted
63
+ copy. Neither needs a `SortedCollection`, which earns its keep only when a
64
+ collection must *stay* sorted as things are added to it — not for sorting
65
+ something once.
66
66
 
67
67
  ## Initialization
68
68