Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After clear(), a map allows double entries #22143

Closed
ratkingsminion opened this issue Sep 1, 2024 · 0 comments · Fixed by #22144
Closed

After clear(), a map allows double entries #22143

ratkingsminion opened this issue Sep 1, 2024 · 0 comments · Fixed by #22144
Labels
Bug This tag is applied to issues which reports bugs. Modules: builtin Bugs and problems, concerning the builtin types in V - array, maps, strings, runes. Status: Confirmed This bug has been confirmed to be valid by a contributor.

Comments

@ratkingsminion
Copy link

ratkingsminion commented Sep 1, 2024

Describe the bug

Code: https://play.vlang.io/p/fe9eccd7aa

fn add(mut m map[int]int, v int) {
	m[v] = v
	println("${m.len} ${m}")
}

mut ints := map[int]int
add(mut ints, 20)
add(mut ints, 34)
add(mut ints, 20) // no double entry!
ints.clear()
add(mut ints, 20)
add(mut ints, 34)
add(mut ints, 20) // oops! double entry!

Reproduction Steps

Run the code above.

Expected Behavior

The last line should show 2 entries only,

Current Behavior

Output:

1 {20: 20}
2 {20: 20, 34: 34}
2 {20: 20, 34: 34}
1 {20: 20}
2 {20: 20, 34: 34}
3 {20: 20, 34: 34, 20: 20}

The last line says there are 3 entries now; but the entry "20" is twice in the map. This only happens after calling clear().

Possible Solution

No response

Additional Information/Context

No response

V version

V 0.4.7 673ac0a

Environment details (OS name and version, etc.)

V full version: V 0.4.7 673ac0a
OS: linux, Debian GNU/Linux 11 (bullseye) (VM)
Processor: 1 cpus, 64bit, little endian, Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz

getwd: /home/admin/playground
vexe: /home/admin/v/v
vexe mtime: 2024-09-01 10:25:26

vroot: OK, value: /home/admin/v
VMODULES: OK, value: .vmodules
VTMP: OK, value: /tmp/v_0

Git version: git version 2.30.2
Git vroot status: Error: fatal: detected dubious ownership in repository at '/home/admin/v'
To add an exception for this directory, call:

	git config --global --add safe.directory /home/admin/v
.git/config present: true

CC version: cc (Debian 10.2.1-6) 10.2.1 20210110
thirdparty/tcc status: Error: fatal: detected dubious ownership in repository at '/home/admin/v/thirdparty/tcc'
To add an exception for this directory, call:

	git config --global --add safe.directory /home/admin/v/thirdparty/tcc
 Error: fatal: detected dubious ownership in repository at '/home/admin/v/thirdparty/tcc'
To add an exception for this directory, call:

	git config --global --add safe.directory /home/admin/v/thirdparty/tcc

Note

You can use the 👍 reaction to increase the issue's priority for developers.

Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.

@ratkingsminion ratkingsminion added the Bug This tag is applied to issues which reports bugs. label Sep 1, 2024
@spytheman spytheman added Modules: builtin Bugs and problems, concerning the builtin types in V - array, maps, strings, runes. Status: Confirmed This bug has been confirmed to be valid by a contributor. labels Sep 1, 2024
spytheman added a commit to spytheman/v that referenced this issue Sep 1, 2024
spytheman added a commit that referenced this issue Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This tag is applied to issues which reports bugs. Modules: builtin Bugs and problems, concerning the builtin types in V - array, maps, strings, runes. Status: Confirmed This bug has been confirmed to be valid by a contributor.
Projects
None yet
2 participants