MapMutator clamps size range values

MapMutator clamps the given min and max values:

jazzer/src/main/java/com/code_intelligence/jazzer/mutation/mutator/collection/MapMutatorFactory.java

Lines 99 to 100 in e13aef0

    
           this.minSize = Math.max(minSize, DEFAULT_MIN_SIZE); 
        
           this.maxSize = Math.min(maxSize, DEFAULT_MAX_SIZE);

This seems to differ from the other mutators such as ListMutator or ArrayMutator which use the given min and max values as is, and instead only perform validation using require(...).

Is it intended that MapMutator differs here in behavior? For consistency, would it make sense to use require here as well to impose restrictions (at least for the minSize)?

fix: support maxSize > 1000 in map mutator

I don't see any reason why the MapMutatator should be treated differently. The minSize parameter is currently not being used

jazzer/src/main/java/com/code_intelligence/jazzer/mutation/mutator/collection/MapMutatorFactory.java

Line 107 in e13aef0

require(minSize == 0, "@WithSize#min != 0 is not yet supported for Map");

but the clamping of maxSize does not serve purpose that I can find. Without clamping maxSize it should be possible to mutate maps with more than DEFAULT_MAX_SIZE elements.

fix: support maxSize > 1000 in map mutator

Navigation Menu

Repository navigation

`MapMutator` clamps size range values #977

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	this.minSize = Math.max(minSize, DEFAULT_MIN_SIZE);
	this.maxSize = Math.min(maxSize, DEFAULT_MAX_SIZE);

MapMutator clamps size range values #977

Description

Activity

simonresch commented on Oct 15, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`MapMutator` clamps size range values #977