Skip to content

Fix error checking on WriteMemory operation#231

Merged
josesimoes merged 1 commit intodevelopfrom
josesimoes-patch-1
Mar 5, 2020
Merged

Fix error checking on WriteMemory operation#231
josesimoes merged 1 commit intodevelopfrom
josesimoes-patch-1

Conversation

@josesimoes
Copy link
Copy Markdown
Member

Description

  • Fix error checking on WriteMemory operation.

Motivation and Context

  • The check was wrongly using a magic value instead of an enum.

How Has This Been Tested?

Screenshots

Types of changes

  • Improvement (non-breaking change that improves a feature, code or algorithm)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Signed-off-by: José Simões jose.simoes@eclo.solutions
Signed-off-by: GITHUB_USER <GITHUB_USER_EMAIL>

@nfbot
Copy link
Copy Markdown
Member

nfbot commented Mar 5, 2020

Hi @josesimoes,

I'm nanoFramework bot.
Thank you for your contribution!

A human will be reviewing it shortly. 😉

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Mar 5, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@josesimoes josesimoes merged commit f9d5779 into develop Mar 5, 2020
@josesimoes josesimoes deleted the josesimoes-patch-1 branch March 5, 2020 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants