1. 22 Nov, 2018 12 commits
  2. 21 Nov, 2018 26 commits
  3. 20 Nov, 2018 2 commits
    • Lioncash's avatar
      file_sys/card_image: Provide named members for the GamecardInfo struct · 820bcee6
      Lioncash authored
      Fills out the struct according to information provided by SwitchBrew
      820bcee6
    • Lioncash's avatar
      common/assert: Add UNIMPLEMENTED_IF and UNIMPLEMENTED_IF_MSG for conditional assertions · 9dcc229d
      Lioncash authored
      Currently, there's no way to specify if an assertion should
      conditionally occur due to unimplemented behavior. This is useful when
      something is only partially implemented (e.g. due to ongoing RE work).
      In particular, this would be useful within the graphics code.
      
      The rationale behind this is it allows a dev to disable unimplemented
      feature assertions (which can occur in an unrelated work area), while
      still enabling regular assertions, which act as behavior guards for
      conditions or states which must not occur. Previously, the only way a
      dev could temporarily disable asserts, was to disable the regular
      assertion macros, which has the downside of also disabling, well, the
      regular assertions which hold more sanitizing value, as opposed to
      unimplemented feature assertions.
      9dcc229d