You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use `slices.Grow` and follow whatever algorithm it uses internally to
pick the next size of the buffer.
So the growth might not be exactly what we asked for, but it should be
optimal from Go runtime point of view.
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
Copy file name to clipboardExpand all lines: .golangci.yml
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# THIS FILE WAS AUTOMATICALLY GENERATED, PLEASE DO NOT EDIT.
2
2
#
3
-
# Generated on 2024-11-26T17:07:18Z by kres 232fe63.
3
+
# Generated on 2025-01-30T12:16:36Z by kres 987bf4d.
4
4
5
5
# options for analysis running
6
6
run:
@@ -17,7 +17,6 @@ output:
17
17
path: stdout
18
18
print-issued-lines: true
19
19
print-linter-name: true
20
-
uniq-by-line: true
21
20
path-prefix: ""
22
21
23
22
# all available settings of specific linters
@@ -134,6 +133,7 @@ linters:
134
133
- perfsprint # complains about us using fmt.Sprintf in non-performance critical code, updating just kres took too long
135
134
- goimports # same as gci
136
135
- musttag # seems to be broken - goes into imported libraries and reports issues there
136
+
- exportloopref # WARN The linter 'exportloopref' is deprecated (since v1.60.2) due to: Since Go1.22 (loopvar) this linter is no longer relevant. Replaced by copyloopvar.
local-%: ## Builds the specified target defined in the Dockerfile using the local output type. The build result will be output to the specified local destination.
0 commit comments