fix binary ninja script erroring on function type parsing #41
Annotations
8 warnings
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Build & Publish:
Il2CppInspector.Common/Cpp/MangledNameBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Build & Publish:
Il2CppInspector.Common/Next/Pointer.cs#L48
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Build & Publish:
Il2CppInspector.Common/Next/PrimitivePointer.cs#L48
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Build & Publish:
Il2CppInspector.Common/FileFormatStreams/ProcessMapReader.cs#L108
Avoid inexact read with 'System.IO.FileStream.Read(byte[], int, int)' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2022)
|
Build & Publish:
Il2CppInspector.CLI/Program.cs#L263
The type 'Utils' in '/home/runner/work/Il2CppInspectorRedux/Il2CppInspectorRedux/Il2CppInspector.CLI/Utils.cs' conflicts with the imported namespace 'Il2CppInspector.Utils' in 'Il2CppInspector.Common, Version=2023.1.0.0, Culture=neutral, PublicKeyToken=null'. Using the type defined in '/home/runner/work/Il2CppInspectorRedux/Il2CppInspectorRedux/Il2CppInspector.CLI/Utils.cs'.
|
Build & Publish:
Il2CppInspector.CLI/Program.cs#L264
The type 'Utils' in '/home/runner/work/Il2CppInspectorRedux/Il2CppInspectorRedux/Il2CppInspector.CLI/Utils.cs' conflicts with the imported namespace 'Il2CppInspector.Utils' in 'Il2CppInspector.Common, Version=2023.1.0.0, Culture=neutral, PublicKeyToken=null'. Using the type defined in '/home/runner/work/Il2CppInspectorRedux/Il2CppInspectorRedux/Il2CppInspector.CLI/Utils.cs'.
|
Build & Publish:
Il2CppInspector.CLI/Program.cs#L177
'System.Reflection.Assembly.Location.get' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
|
Loading