Skip to content

Update dependencies & remove warnings - cargo 1.92.0; added CI build & test#19

Open
etjones wants to merge 6 commits intoFormlabs:masterfrom
etjones:feature/remove_warnings_2025-12-11
Open

Update dependencies & remove warnings - cargo 1.92.0; added CI build & test#19
etjones wants to merge 6 commits intoFormlabs:masterfrom
etjones:feature/remove_warnings_2025-12-11

Conversation

@etjones
Copy link

@etjones etjones commented Dec 15, 2025

No feature changes, but updates dependencies & removes compile warnings for cargo 1.92.0, late 2025

  • Upgrade nalgebra-glm from 0.13 to 0.20
  • Upgrade nom from 6.0 to 7
  • Removed build warnings. These were almost all to add explicit lifetimes to return types, like:
    • (old) fn to_type(&'a self, type_map: &mut TypeMap<'a>) -> Type {
    • (new) `fn to_type(&'a self, type_map: &mut TypeMap<'a>) -> Type<'a> {
  • Allow dead code in express/src/parse.rs; unused fields are meant for library consumers, so we want to keep them present even if they're not yet used.
  • Added CI build and test with cargo/rustc 1.92.0. Building on Ubuntu only.

Locally developed on a MacOS 15.6.1 system.

- Add #![allow(dead_code)] at module level for AST struct fields
  (these are meant for library consumers)
- Fix lifetime elision warnings by adding explicit '_ annotations
  to IResult type signatures throughout parse.rs
- Update alias macro to handle lifetime and non-lifetime cases separately
- Fix SimpleId::parse, Expression::parse, and SimpleExpression::parse
  to use explicit lifetime annotations
- Update nom dependency in express/Cargo.toml and step/Cargo.toml
- Fix fold_many0/fold_many1 API changes: init parameter changed from
  value to closure in nom 7
  - binary_literal: 0 -> || 0
  - encoded_string_literal: String::new() -> String::new
  - simple_string_literal: String::new() -> String::new

All 49 tests pass.
- Update nalgebra-glm in gui/Cargo.toml, nurbs/Cargo.toml, triangulate/Cargo.toml
- This also upgrades nalgebra from 0.27.1 to 0.34.1
- Resolves the future-incompatibility warning about trailing semicolons in macros

No code changes required - the API is backwards compatible for our usage.
All 49 tests pass.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant