chapel-lang/chapel

Bug with `isPOD` and generic record types

Open

#24,172 opened on Jan 9, 2024

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Chapel (446 forks)auto 404
area: Compilergood first issuetype: Bug

Repository metrics

Stars
 (2,010 stars)
PR merge metrics
 (PR metrics pending)

Description

use Types;

record r { type T; var x: T; }

proc main() {
  writeln(isPOD(r(?)));
}

Foo.chpl:3: error: cannot default-initialize a variable with generic type
Note: This source location is a guess.
note: '<temporary>' has generic type 'r'
note: cannot find initialization point to split-init this variable

In the debugger I can see that it's referring to the auto-generated deinit which has its resolution triggered by resolveAutoCopyEtc, called from propagateNotPod.

Contributor guide

Research direction
Investigate the resolution of `isPOD` for generic records and see why it triggers default initialization. Trace the call from `propagateNotPod` to `resolveAutoCopyEtc` and understand the conditions that lead to the error.
Tech stack
cpp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Chapel
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40