You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems inappropriate that u8, u16, and u32 are leaked from USBAPI.h, which in turn is included in Arduino.h, and thus polluting the global namespace:
If you try to define u16 yourself as using u16 = uint16_t; while including Arduino.h, you'll get a compilation error because this alias conflicts with the one from USBAPI.h.
Is this behavior intended?
The text was updated successfully, but these errors were encountered:
Sounds wrong to me, I'd be in favor of removing them. Especially since (at first glance) it seems the header file does not actually use these types at all either.
It seems inappropriate that
u8
,u16
, andu32
are leaked fromUSBAPI.h
, which in turn is included inArduino.h
, and thus polluting the global namespace:ArduinoCore-avr/cores/arduino/USBAPI.h
Lines 29 to 31 in 42fa4a1
If you try to define
u16
yourself asusing u16 = uint16_t;
while includingArduino.h
, you'll get a compilation error because this alias conflicts with the one fromUSBAPI.h
.Is this behavior intended?
The text was updated successfully, but these errors were encountered: