uber/queryparser

Name structures don't support NFData instances

Open

#15 opened on Dec 9, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Haskell (1,079 stars) (145 forks)batch import
good first issue

Description

Since our queries and catalogs can get large, we should have controls over strictness, including using deepseq. Currently, that is not supported.

Contributor guide

Tech stack
None
Domain
backendperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Haskelldeepseqqueryparser codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Examine the source code for name structures (likely in modules like QueryParser.Name or similar) in the queryparser library. Identify all data types that need NFData instances. Add appropriate deriving clauses or manual instances for deepseq, and ensure Control.DeepSeq is imported. No existing comments or PRs provide further context.