Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
G
GLib
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 925
    • Issues 925
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 62
    • Merge Requests 62
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • GLib
  • Issues
  • #1446

Closed
Open
Opened Jul 13, 2018 by Emmanuele Bassi@ebassi👣Maintainer0 of 1 task completed0/1 task

Follow-up from "Document difference between g_assert() and g_assert_*() wrt G_DISABLE_ASSERT"

The following discussion from !174 (merged) should be addressed:

  • @ebassi started a discussion:

    I completely forgot, but: the behaviour of g_test_init() when used with G_DISABLE_ASSERT should be documented.

Assignee
Assign to
2.58
Milestone
2.58 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/glib#1446