Not important, but when overriding a method that can return null, it seems preferable to put @Override first, followed by what it's overriding (which includes the @Nullable). Also remove explicit @NonNull use in the core library. @NonNull is propagated by default, so this is redundant. PiperOrigin-RevId: 296188379
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| av1 | Loading commit data... | |
| cast | Loading commit data... | |
| cronet | Loading commit data... | |
| ffmpeg | Loading commit data... | |
| flac | Loading commit data... | |
| gvr | Loading commit data... | |
| ima | Loading commit data... | |
| jobdispatcher | Loading commit data... | |
| leanback | Loading commit data... | |
| mediasession | Loading commit data... | |
| okhttp | Loading commit data... | |
| opus | Loading commit data... | |
| rtmp | Loading commit data... | |
| vp9 | Loading commit data... | |
| workmanager | Loading commit data... | |
| README.md | Loading commit data... |