You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Description of work
#### Summary of work
`napi` was apparently written before pass-by-reference was a thing. Or
at least it did not make proper use of pass-by-reference, instead
passing `void**` objects to enable edited the `void*` in certain
methods.
This replaces the four methods in `napi` and `napi5` that use `void**`
to instead use `void*&`.
Refs #38332
#### Further detail of work
Using pass-by-reference means the `void*` object can be directly
modified, without having to use dereferencing. This impacted the
internals of the methods.
The few places in the code that call these methods were also changed,
including in the `napi` tests.
### To test:
This is a minor refactor that should not change behavior. If NeXus files
can still be opened, closed, reopened, and flushed (which the existing
unit tests prove) then everything is fine.
*This does not require release notes* because it is way under the hood,
away from users.
---
### Reviewer
Please comment on the points listed below ([full
description](http://developer.mantidproject.org/ReviewingAPullRequest.html)).
**Your comments will be used as part of the gatekeeper process, so
please comment clearly on what you have checked during your review.** If
changes are made to the PR during the review process then your final
comment will be the most important for gatekeepers. In this comment you
should make it clear why any earlier review is still valid, or confirm
that all requested changes have been addressed.
#### Code Review
- Is the code of an acceptable quality?
- Does the code conform to the [coding
standards](http://developer.mantidproject.org/Standards/)?
- Are the unit tests small and test the class in isolation?
- If there is GUI work does it follow the [GUI
standards](http://developer.mantidproject.org/Standards/GUIStandards.html)?
- If there are changes in the release notes then do they describe the
changes appropriately?
- Do the release notes conform to the [release notes
guide](https://developer.mantidproject.org/Standards/ReleaseNotesGuide.html)?
#### Functional Tests
- Do changes function as described? Add comments below that describe the
tests performed?
- Do the changes handle unexpected situations, e.g. bad input?
- Has the relevant (user and developer) documentation been
added/updated?
Does everything look good? Mark the review as **Approve**. A member of
`@mantidproject/gatekeepers` will take care of it.
### Gatekeeper
If you need to request changes to a PR then please add a comment and set
the review status to "Request changes". This will stop the PR from
showing up in the list for other gatekeepers.
0 commit comments