obs-browser: Fix compiler warnings #327
No reviewers
Labels
No labels
area/accessibility
area/dependency
Confirmed
Crash Report
Delayed
Design Issue
Duplicate
Feedback required
Good first issue
kind/bug
kind/cleanup
kind/enhancement
platform/linux
platform/macos
platform/windows
priority/high
Question
Request for Comments
Seeking Other Contributors
Seeking Testers
Won't Fix / By Design
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-obsproject/obs-browser!327
Loading…
Reference in a new issue
No description provided.
Delete branch "fix-browser-warnings"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
This fixes warnings found with GCC on Linux.
Motivation and Context
Warnings are annoying.
How Has This Been Tested?
Compiled to see if warnings went away.
Types of changes
Checklist:
This is a bad idea, that switch is meant to fall through (otherwise for example having
Fullaccess wouldn't give you access toAdvancedand below).However, this PR does prove RytoEX's point about the switch not being particularly beautiful. Feel free to refactor it.
Yeah my understanding was that this is intentional.
To avoid compiler warnings, wouldn't
[[fallthrough]]from C++17 be more appropriate?Supported in:
https://en.cppreference.com/w/cpp/language/attributes/fallthrough
Updated it to use the fallthrough statements