0324e8d2a2
Make sure removed/resetted user valeus get garbage collected
...
Since our userData slice isn't shrunk when we delete values, it can
still keep pointing to things that have been removed. Set these pointers
to nil so that the key and value can be garbage collected.
Fixes https://github.com/valyala/fasthttp/issues/1812
2024-07-28 11:06:17 +02:00
f196617f55
chore: Use 'any' instead of 'interface{}' ( #1666 )
...
gofmt -w -r "interface{} -> any" -l .
2023-11-24 11:33:04 +01:00
ffdf59d04c
Enable gofumpt linter; format code gofumpt -w . ( #1576 )
2023-06-13 15:18:59 +02:00
9961079196
Fix userdata re-use after Remove
...
See also: https://github.com/valyala/fasthttp/pull/1298
2022-05-11 16:11:18 +02:00
7a5afddf5b
Use %v for errors and %q for strings ( #1262 )
...
Mostly in tests.
2022-04-01 18:11:16 +02:00
7fdd5261e8
feat: a new userData API Remove ( #1117 )
...
* feat:userData new api "delete"
* ctx api `remove`
* rename
* modify
2021-10-08 17:45:45 +02:00
c3d82ca3a4
Speed up testing by running tests in parallel
2019-10-16 10:20:13 +02:00
eafcb74ce5
Call Close on user values stored via RequestCtx.SetUserValue if these values implement io.Closer
2016-02-05 12:50:58 +02:00
b805a92a29
Fixed a typo
2015-12-16 16:52:28 +02:00
b00a213a93
Moved ctx.UserValue from standard map to custom userData. This should improve its' performance for common case when ctx contains up to 10 user values
2015-12-11 16:40:55 +02:00
Erik Dubbelboer
Oleksandr Redko
tyltr
Aliaksandr Valialkin