Docs/defensive-coding-guide
2
0
Fork 0
Code Issues 3 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Mention importance of enforcing proper coding style #15

New issue
Open
opened 2020-10-13 07:57:44 +00:00 by ueno · 0 comments
ueno commented 2020-10-13 07:57:44 +00:00
Contributor
Copy link

Although it might be beyond the scope of this document, I think it's good to mention that inconsistent coding style can cause severe security issue:
https://www.imperialviolet.org/2014/02/22/applebug.html

Although it might be beyond the scope of this document, I think it's good to mention that inconsistent coding style can cause severe security issue: https://www.imperialviolet.org/2014/02/22/applebug.html
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
Closed As
Duplicate
Closed with the reason of Duplicate

  
Closed As
Fixed
Closed with the reason of Fixed

  
Closed As
Insufficient data
Closed with the reason of Insufficient data

  
Closed As
Invalid
Closed with the reason of Invalid

No labels
Closed As
Duplicate
Closed As
Fixed
Closed As
Insufficient data
Closed As
Invalid
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Docs/defensive-coding-guide#15
No description provided.
Delete branch "%!s()"

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?