mabdi / mabdi/small-amp

Method Purity

Open
#92 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Smalltalk
Stars
6
Forks
4
PR merge metrics
No merged PRs in 30d

Description

We need to enhance method-purity detection.
example: this method (MADescription>>#accessor) is pure, but we indicate it as non-pure because. it writes an instance variable.

accessor
	"Answer the access-strategy of the model-value described by the receiver."

	^ accessor ifNil: [ accessor := self class defaultAccessor ]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the method-purity detection entry point for MADescription>>#accessor and trace how its instance-variable assignment is classified. Confirm the expected behavior using the supplied Smalltalk example; the work is done when this accessor is recognized as pure without weakening detection of genuinely impure methods.

Written by the indexing model from the issue text.

Assessment

Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.