Skip to content
GitLab
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
LIGO
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
6
Snippets
Groups
Projects
Show more breadcrumbs
ligolang
LIGO
Merge requests
!2699
[Chore] Fix bug with wrong `to_point` `to_byte` conversion
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
[Chore] Fix bug with wrong `to_point` `to_byte` conversion
xjie6/#1689-error-recovery-improvements
into
dev
Overview
1
Commits
4
Pipelines
5
Changes
5
Merged
Iurii Kravchenko
requested to merge
xjie6/#1689-error-recovery-improvements
into
dev
1 year ago
Overview
1
Commits
4
Pipelines
5
Changes
5
Expand
Motivation and Context
Related issues
Resolves .
Checklist for the LIGO Language Server
I checked whether I need to update the
README.md
file for the
plugin
and did so if necessary:
If I implemented a new LSP request, I added it to the list of supported features that may be disabled
If I implemented a new LSP method, I added it to the list of supported functionality
I checked that my changes work in Emacs, Vim, and Visual Studio Code
(Before merging) The commit history is squashed and prettified, and follows the
Serokell commit policy
, or the MR is set to squash the commits
Description
Component
compiler
website
webide
vscode-plugin
debugger
Types of changes
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 not work as expected)
Performance improvement (non-breaking change that improves performance)
None (change with no changelog)
Changelog
Checklist:
Changes follow the existing coding style (use
dune @fmt
to check).
Tests for the changes have been added (for bug fixes / feature).
Documentation has been updated.
Changelog description has been added (if appropriate).
Start titles under
## Changelog
section with #### (if appropriate).
There is no image or uploaded file in changelog
Examples in changed behaviour have been added to the changelog (for breaking change / feature).
Edited
1 year ago
by
Iurii Kravchenko
0
0
Merge request reports
Activity
All activity
Filter activity
Deselect all
Approvals
Assignees & reviewers
Comments (from bots)
Comments (from users)
Commits & branches
Edits
Labels
Lock status
Mentions
Merge request status
Tracking
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Please
register
or
sign in
to reply
Loading