chpl version 2.9.0
built with LLVM version 22.1.7
available LLVM targets: xcore, x86-64, x86, wasm64, wasm32, ve, systemz, spirv, spirv64, spirv32, sparcel, sparcv9, sparc, riscv64be, riscv32be, riscv64, riscv32, ppc64le, ppc64, ppc32le, ppc32, nvptx64, nvptx, msp430, mips64el, mips64, mipsel, mips, loongarch64, loongarch32, lanai, hexagon, bpfeb, bpfel, bpf, avr, thumbeb, thumb, armeb, arm, amdgcn, r600, aarch64_32, aarch64_be, aarch64, arm64_32, arm64
Copyright 2020-2026 Hewlett Packard Enterprise Development LP
Copyright 2004-2019 Cray Inc.
(See LICENSE file for more details)
CHPL_TARGET_PLATFORM: darwin
CHPL_TARGET_COMPILER: llvm
CHPL_TARGET_ARCH: arm64
CHPL_TARGET_CPU: native *
CHPL_LOCALE_MODEL: flat
CHPL_COMM: none *
CHPL_TASKS: qthreads
CHPL_LAUNCHER: none
CHPL_TIMERS: generic
CHPL_UNWIND: system
CHPL_TARGET_MEM: jemalloc
CHPL_ATOMICS: cstdlib
CHPL_GMP: system *
CHPL_HWLOC: bundled
CHPL_RE2: bundled *
CHPL_LLVM: system *
CHPL_AUX_FILESYS: none
Apple clang version 21.0.0 (clang-2100.1.1.101)
Target: arm64-apple-darwin25.5.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
Summary of Problem
Description:
Mason allows adding names with conflicts as dependencies, including the current project. For example, when in the Parquet GitHub repository cloned locally, it is possible to add Parquet as a dependency, which will result in name conflicts (i.e.,
Parquet.chplfrom the Mason registry versusParquet.chplfrom the current directory).Is this issue currently blocking your progress?
No.
Steps to Reproduce
95d4fac87aada97d314eba8af05b21027e6704e6, and navigate to theParquet/directory.mason search --update, followed bymason add Parquet@0.1.2. The dependency add succeeds.Configuration Information
chpl --version:$CHPL_HOME/util/printchplenv --anonymize:gcc --versionorclang --version: