Skip to content

Conversation

@lawmaestro
Copy link
Contributor

@lawmaestro lawmaestro commented Jan 8, 2017

Checklist

Not all of these might apply to your change but the more you are able to check
the easier it will be to get your contribution merged.

  • CI passes
  • Description of proposed change
  • Documentation (README, code doc blocks, etc) is updated
  • Existing issue is referenced if there is one
  • Unit tests for the proposed change

@mrtazz
Copy link
Owner

mrtazz commented Apr 22, 2017

Can you please make sure this change has unit tests, works on CI, and has an example usage documented in the README?

@mrtazz mrtazz added the failing-ci the PR doesn't work on CI because of a code problem label Mar 8, 2018
@lawmaestro
Copy link
Contributor Author

So this is failing as the code isn't compiled with C11 support. Is there any good reason we can't baseline to this now? Or as a minimum have that turned on for the tests?

@mrtazz
Copy link
Owner

mrtazz commented Feb 12, 2020

C11 support is fine to add I think. We have other places now that kinda need it anyways.

@lawmaestro
Copy link
Contributor Author

C11 support is fine to add I think. We have other places now that kinda need it anyways.

Looks like C11 support has been added for the test suite now :) I've merged in latest master & resolved the conflict. Let me know your thoughts 👍

@mrtazz
Copy link
Owner

mrtazz commented Mar 3, 2020

perfect! thank you for the contribution!

@mrtazz mrtazz merged commit eeb00a8 into mrtazz:master Mar 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

failing-ci the PR doesn't work on CI because of a code problem

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants