Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed SIG-Core meeting agenda (Date:21/JUL/2021/Time: 0900 PST, 1700 BST) #8

Closed
amzn-pratikpa opened this issue Jul 14, 2021 · 4 comments
Labels
mtg-agenda Tag for meeting proposed and accepted agendas

Comments

@amzn-pratikpa
Copy link
Collaborator

amzn-pratikpa commented Jul 14, 2021

Meeting Details

The SIG-Core Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

SIG Updates

What happened since the last meeting?

  • Discussed SIG Charter and agreed it was too broad.
  • Consensus was that a mission statement would help narrow the focus of the charter

Meeting Agenda

Please list any additional items you would like to add to the agenda in the comments.

@amzn-pratikpa amzn-pratikpa added the mtg-agenda Tag for meeting proposed and accepted agendas label Jul 14, 2021
@amzn-pratikpa amzn-pratikpa changed the title Proposed SIG-Core meeting agenda (Date/Time: TBD) Proposed SIG-Core meeting agenda (Date:21/JUL/2021/Time: 0900 PST, 1700 BST) Jul 16, 2021
@hultonha
Copy link
Collaborator

hultonha commented Oct 10, 2021

I would be interested to know if there's interest in adding the Guideline Support Library (GSL) https://github.com/microsoft/GSL to AzCore (potentially AzFramework).

The GSL has some incredibly useful types (e.g. gsl::span, coming in std:: in C++20). Adopting it would help us conform to the C++ Core Guidelines that build on top of this library (https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines). There's some useful techniques gaining wider use such as using zstring to explicitly refer to a null terminated string (as opposed to const char* that could refer to a single character or char array).

The library is designed to encourage safe and secure use of C++ adopting the zero-overhead mindset we've come to expect from C++ libraries.

This would likely need to be an RFC before it can be adopted but I'd be interested to take the temperature of the room to see if there's interest or not before spending more time on it.

Update - I foolishly posted this on the wrong agenda, it's now moved here - #13 (comment) (that'll teach me for trying to do it on mobile 🤦‍♂️)

@amzn-pratikpa
Copy link
Collaborator Author

I would be interested to know if there's interest in adding the Guideline Support Library (GSL) https://github.com/microsoft/GSL to AzCore (potentially AzFramework).

The GSL has some incredibly useful types (e.g. gsl::span, coming in std:: in C++20). Adopting it would help us conform to the C++ Core Guidelines that build on top of this library (https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines). There's some useful techniques gaining wider use such as using zstring to explicitly refer to a null terminated string (as opposed to const char* that could refer to a single character or char array).

The library is designed to encourage safe and secure use of C++ adopting the zero-overhead mindset we've come to expect from C++ libraries.

This would likely need to be an RFC before it can be adopted but I'd be interested to take the temperature of the room to see if there's interest or not before spending more time on it.

@hultonha Did you mean to comment on the other meeting proposal? #13

@hultonha
Copy link
Collaborator

@amzn-pratikpa I did sorry! 🤦‍♂️ Will move now! 😝

@hultonha
Copy link
Collaborator

@amzn-pratikpa I had a thought, should we close this issue now as it's been and gone to try and give idiots like me a fighting chance to post on the right one? 😛 Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mtg-agenda Tag for meeting proposed and accepted agendas
Projects
None yet
Development

No branches or pull requests

2 participants