Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

English documentation updates up to v0.8.17-65-g2201526a9 (2022-09-28) #40

Open
wants to merge 1,009 commits into
base: develop
Choose a base branch
from

Conversation

soldocsbot
Copy link

This is an automatically-generated sync PR to bring this translation repository up to date with the state of the English documentation as of 2022-09-28 (commit 2201526a).

How to work on a sync PR

Resolve conflicts and translate newly added text

  • The PR includes all documentation changes from the main repository since the last time a sync PR was merged. If this translation repository is fully caught up with the English version, translate any newly added English text you see here by pushing more commits to the PR. However, if the translation is incomplete, you may prefer to leave the text added in this PR and add it to your translation checklist to handle at a later time.
  • Scan the PR for merge conflict markers. If there were changes in the English text that has already been translated, the PR will contain merge conflicts that need to be resolved:
    <<<<<<< HEAD
        El valor más grande representable por el tipo ``T``.
    =======
        The smallest value representable by type ``T``.
    >>>>>>> 800088e38b5835ebdc71e9ba5299a70a5accd7c2
    The top part of the conflict is the current translation (corresponding to the old English text), the bottom shows the new English text. To solve the conflict simply translate the new text, possibly reusing parts of the current translation. After doing so, do not forget to remove the conflict markers.
  • You may get conflicts also if there were structual changes that did not affect the meaning of the text and therefore do not require retranslation. For example when text is moved from one page to another, you will find matching conflicts in two places and the solution is to move the translation to the new spot. If only whitespace changed, it may even seem like there was no change at all but if there is a conflict, there is always a reason, however trivial it may be. Be careful, though, because there is a possibility that the text was both moved and modified.

Work on one sync PR at a time

  • Sync PRs are produced by the translation bot in regular intervals as long as there are changes in the English documentation. You will not lose any updates by closing this PR. The next sync PR will also include them. The latest sync PR will always include all changes that need to be done. If you haven't worked on any sync PR yet and there are several open sync PRs in your repo, choose the latest (newest) one to get started.
  • It is recommended to work only on one sync PR at a time. Close this PR if you are already working on a different one.
  • Once you merge this PR, the conflict resolutions and new commits you pushed to it are likely to cause conflicts with other open sync PRs. It is possible solve these conflicts if you are proficient with git and fully understand what changed in which PR, but for simplicity it is recommended to close all pending sync PRs and wait for a fresh one, which will no longer include the merged changes.

Do not squash merge or rebase this PR

Rebasing or squashing a sync PR erases the information about the commits that the changes originally came from, which will result in extra conflicts in the next sync PR.
If you do it by accident, don't worry - simply make sure to handle the next sync PR properly, which will restore the missing commits.

Review checklist

The following files were modified in this pull request. Please review them before merging the PR:

ekpyron and others added 30 commits August 8, 2022 13:49
Fix wrong cleanup when copying from calldata to memory.
Set release date for 0.8.16 and update the bug list
The solidity docs and [Inline assembly memory management](https://docs.soliditylang.org/en/v0.8.15/assembly.html#memory-management) suggest the actual allocate-able memory starts from `0x80`. The above yul example defaults the free memory pointer to `0x60` in initialisation cases.
…or-on-update

`update_bugs_by_version.py`: don't fail when the list gets updated
Docs — Minor grammar fixes in `abi-spec.rst`
…InDocs

[Docs] Fixed link to internal-function-calls
r0qs and others added 28 commits September 22, 2022 14:51
Co-authored-by: Kamil Śliwak <[email protected]>
Co-authored-by: Daniel Kirchner <[email protected]>
Workflow to label and comment stale pull requests
…fier

Add code style rule for std:: qualifier
Fix stripping in CLI tests does not produce correct JSON formatting
Add v0.6.0 change notes for inline assembly opcode syntax changes.
…ke it more clear what this function is supposed to be used for.
renames lspAssert() to lspRequire + documentation
EVMHost: Simplify some code and document functions
And also refactor resultWithFailure
…r-ambigious-call

Update ambiguous CVC4::BitVector ctor call
Replace use of boost::adapters::filtered with ranges::views::filter
EVMHost: a few more simplifications
Drop implicit alignment argument from FixedHash (and improve FunctionSelector helpers)
EVMHost: Calculate address for CREATE properly
Copy link

@sujilee91 sujilee91 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No conflicts on this sync

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.