Skip to content

Conversation

@ChrisRackauckas
Copy link
Member

Summary

This PR updates the return code (retcode) documentation to reflect the current enum-based implementation instead of the outdated symbol-based approach.

Changes

  • Updated docs/src/basics/solution.md to explain that return codes are now enum values
  • Added proper usage example showing SciMLBase.successful_retcode(sol)
  • Added warning about the deprecated sol.retcode == :Success pattern
  • Fixed incorrect usage in docs/src/basics/faq.md (was passing sol.retcode, should be just sol)
  • Added link to the SciMLBase ReturnCode documentation for complete reference

Context

As pointed out in issue #734, the documentation was outdated and still described return codes as symbols (e.g., :Success) when they are now implemented as an enum using EnumX.jl.

Example

The documentation now shows the correct way to check for successful solutions:

# Correct (new way)
SciMLBase.successful_retcode(sol)

# Incorrect (old way - now deprecated)
sol.retcode == :Success

Fixes #734

🤖 Generated with Claude Code

…#734)

- Update retcode documentation to explain they are now enum values, not symbols
- Add proper usage example with SciMLBase.successful_retcode(sol)
- Add warning about deprecated sol.retcode == :Success pattern
- Fix incorrect usage in FAQ (was sol.retcode, should be just sol)
- Add link to SciMLBase ReturnCode documentation for complete reference

This addresses the issue where the documentation was outdated and still
described return codes as symbols instead of the current enum implementation.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@ChrisRackauckas ChrisRackauckas merged commit da6b151 into master Jul 23, 2025
1 of 3 checks passed
@ChrisRackauckas ChrisRackauckas deleted the fix-issue-734-retcode-docs branch July 23, 2025 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Return code documentation describes symbols instead of enum

2 participants