Update tips.md #52
EkopalypseAnnotations
10 errors, 11 warnings, and 8 notices
|
build:
util/winapi/winapi.v#L252
unknown function: C.LPDWORD
|
|
build:
util/winapi/winapi.v#L252
`C.LPDWORD(number_of_bytes_read)` (no value) used as value in argument 4 to `C.ReadFile`
|
|
build:
util/io_handler/io_handler.v#L15
assigning `0` to a reference field is only allowed in `unsafe` blocks
|
|
build:
util/io_handler/io_handler.v#L20
assigning `0` to a reference field is only allowed in `unsafe` blocks
|
|
build:
util/io_handler/io_handler.v#L25
assigning `0` to a reference field is only allowed in `unsafe` blocks
|
|
build:
util/io_handler/io_handler.v#L40
cannot use `&i8` as `&u8` in argument 1 to `tos`
|
|
build:
util/io_handler/io_handler.v#L59
cannot use `&i8` as `&u8` in argument 1 to `tos`
|
|
build:
scintilla/lsp_extension.v#L73
cannot use literal signed integer as `usize` in argument 2 to `scintilla.Editor.call`
|
|
build:
util/procman/procman.v#L72
assigning `0` to a reference field is only allowed in `unsafe` blocks
|
|
build:
util/procman/procman.v#L73
assigning `0` to a reference field is only allowed in `unsafe` blocks
|
|
build
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build:
NppLsp.v#L89
`[attr]` has been deprecated, use `@[attr]` instead
|
|
build:
NppLsp.v#L94
`[attr]` has been deprecated, use `@[attr]` instead
|
|
build:
NppLsp.v#L99
`[attr]` has been deprecated, use `@[attr]` instead
|
|
build:
NppLsp.v#L116
`[attr]` has been deprecated, use `@[attr]` instead
|
|
build:
NppLsp.v#L313
`[attr]` has been deprecated, use `@[attr]` instead
|
|
build:
NppLsp.v#L337
`[attr]` has been deprecated, use `@[attr]` instead
|
|
build:
NppLsp.v#L476
`[attr]` has been deprecated, use `@[attr]` instead
|
|
build:
NppLsp.v#L690
`[attr]` has been deprecated, use `@[attr]` instead
|
|
build:
NppLsp.v#L691
`[attr]` has been deprecated, use `@[attr]` instead
|
|
build:
notepadpp/notepadpp.v#L52
`[attr]` has been deprecated, use `@[attr]` instead
|
|
build:
scintilla/scintilla.v#L72
uninitialized `fn` struct fields are not allowed, since they can result in segfaults; use `?fn` or `@[required]` or initialize the field with `=` (if you absolutely want to have unsafe function pointers, use `= unsafe { nil }`)
|
|
build:
scintilla/scintilla.v#L74
uninitialized `fn` struct fields are not allowed, since they can result in segfaults; use `?fn` or `@[required]` or initialize the field with `=` (if you absolutely want to have unsafe function pointers, use `= unsafe { nil }`)
|
|
build:
scintilla/scintilla.v#L76
uninitialized `fn` struct fields are not allowed, since they can result in segfaults; use `?fn` or `@[required]` or initialize the field with `=` (if you absolutely want to have unsafe function pointers, use `= unsafe { nil }`)
|
|
build:
dialogs/console/console.v#L60
uninitialized `fn` struct fields are not allowed, since they can result in segfaults; use `?fn` or `@[required]` or initialize the field with `=` (if you absolutely want to have unsafe function pointers, use `= unsafe { nil }`)
|
|
build:
dialogs/diagnostics/diagnostics_dialog.v#L69
uninitialized `fn` struct fields are not allowed, since they can result in segfaults; use `?fn` or `@[required]` or initialize the field with `=` (if you absolutely want to have unsafe function pointers, use `= unsafe { nil }`)
|
|
build:
dialogs/references/references.v#L81
uninitialized `fn` struct fields are not allowed, since they can result in segfaults; use `?fn` or `@[required]` or initialize the field with `=` (if you absolutely want to have unsafe function pointers, use `= unsafe { nil }`)
|
|
build:
dialogs/symbols/symbols.v#L108
uninitialized `fn` struct fields are not allowed, since they can result in segfaults; use `?fn` or `@[required]` or initialize the field with `=` (if you absolutely want to have unsafe function pointers, use `= unsafe { nil }`)
|
|
build:
NppLsp.v#L83
uninitialized `fn` struct fields are not allowed, since they can result in segfaults; use `?fn` or `@[required]` or initialize the field with `=` (if you absolutely want to have unsafe function pointers, use `= unsafe { nil }`)
|