Repository navigation
Update fp_mojo to 1.0.1 - #413
Open
anatolvitold wants to merge 1 commit into
Open
anatolvitold wants to merge 1 commit into
anatolvitold wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates FP Mojo from 1.0.0 to 1.0.1, adding consuming iterator method chains with native standard-library interoperability.
The recipe builds from the published v1.0.1 tag, keeps build number 0 for the new version, and adds
iteration_chaining.mojoto the existing package tests. That example coversiterated,flat_map, both list-collection aliases, standardenumerate, and borrowing a source collection.The build continues to use
mojo precompilewithmojo-compiler =1.1.0; the runtime pin remainsmojo-compiler >=1.1.0,<1.2.0a0.Validation:
-I src: quickstart, expression, config_parser and iteration_chaining.lib/mojo/fp.mojoc, the Apache-2.0 license, and the expected runtime dependency. YAML and whitespace checks passed.The same-version build-number bump below does not apply because the version changed.
Checklist
recipe.yamlfile specifies which version(s) of MAX is compatible with my project (see here for an example). If not, my package is compatible with both 24.5 and 24.6.0(for new packages, or if the version changed).