C#8 nullable references implementation#75
Conversation
|
Whether a libvlc API can or cannot return
I say we should consider all strings (and possibly any pointers) possibly null. I understand it makes the C# 8 nullable support less appealing for us, but that's just the reality of native code interop. |
|
What's left to be done here?
|
0946fa4 to
09e9e8e
Compare
|
Just
I might have missed some though... When you say "all projects", do you mean the samples as well? |
No need to convert the sample projects, but maybe adding a small sample to libvlcsharp-samples displaying what calling a few libvlcsharp APIs with the netstandard2.1 target looks like? |
42dee63 to
97caaaa
Compare
|
Is this good to merge? @jeremyVignelles |
|
We can now remove the #nullable enable/restore lines I added in LibVLCSharp/Shared/MediaPlayerElement files waiting this PR. |
|
done. I don't think there's anything left on my side. I'm ok for merging |
We need to reference a pre-release version of Uno.UI
c206e39 to
0a9337d
Compare
|
🎉 |
Description of Change
This changes allows to use LVS with nullable annotations.
<Nullable>enable</Nullable>in csprojsThis is currently a Work In Progress, only LibVLCSharp and LibVLCSharp.Forms has been implemented.
Issues Resolved
API Changes
Not sure if there is any. Intent will be explained more clearly.
Platforms Affected
Not applicable
Behavioral/Visual Changes
When using LVS with nullable references enabled, Visual studio can warn you about a wrong usage of the API regarding null values.
Before/After Screenshots
Not applicable
Testing Procedure
Call every API and see if it works? 😄
PR Checklist