← Back to home
Comparison · Analytics

haze vs incase

A side-by-side editorial comparison of haze and incase — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

haze vs incase: at a glance

Featurehazeincase
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesneuroimaging, mesh-processing, interpolation, r-packagedata-wrangling, recoding, tidyverse, api-deprecation
Last editorial update6h ago47m ago
WebsiteVisit →Visit →

What is haze?

Four dormant years end with a modernization pass and an off-by-one fix in the C++ core

haze does nearest-neighbour smoothing and k-d tree interpolation on brain surface meshes. It sat untouched from April 2022 until July 2026, when a single release modernized it for current R versions and corrected an off-by-one error in the C++ code. It is not on CRAN and never will be — the package exceeds 50MB against CRAN's 5MB ceiling, a constraint its own initial release notes acknowledge.

Read the full haze trajectory →

What is incase?

A safer case_when that keeps hardening its guarantees while realigning to tidyverse naming.

incase supplies in_case(), switch_case(), grep_case() and fn_case() as vectorised recoding functions in the dplyr::case_when idiom, with _fct and _list variants that return factors or lists instead of forcing atomic type conversion. The 0.4.0 release deprecates the undotted preserve, default and ordered arguments in favour of dotted forms, starting a removal clock, and adds .exhaustive to error on unmatched inputs.

Read the full incase trajectory →

haze vs incase: editorial side-by-side

H
haze
ANALYTICS
2.5

Four dormant years end with a modernization pass and an off-by-one fix in the C++ core

◆ Current state

haze does nearest-neighbour smoothing and k-d tree interpolation on brain surface meshes. It sat untouched from April 2022 until July 2026, when a single release modernized it for current R versions and corrected an off-by-one error in the C++ code. It is not on CRAN and never will be — the package exceeds 50MB against CRAN's 5MB ceiling, a constraint its own initial release notes acknowledge.

◆ Where it's heading

The July 2026 release arrived 56 minutes after its sibling regfusionr 0.3.0 from the same maintainer, which is the tell: this is a maintainer sweeping a set of related neuroimaging packages back into working order, not independent development on haze itself. haze is the dependency, regfusionr the consumer, and the substantive work sits on the regfusionr side. The off-by-one correction is the only change here that alters results.

◆ Prediction

Expect haze to move only when a downstream dfsp-spirit package needs it to — its cadence is driven by the sibling packages, not by its own roadmap.

I
incase
ANALYTICS
0.0

A safer case_when that keeps hardening its guarantees while realigning to tidyverse naming.

◆ Current state

incase supplies in_case(), switch_case(), grep_case() and fn_case() as vectorised recoding functions in the dplyr::case_when idiom, with _fct and _list variants that return factors or lists instead of forcing atomic type conversion. The 0.4.0 release deprecates the undotted preserve, default and ordered arguments in favour of dotted forms, starting a removal clock, and adds .exhaustive to error on unmatched inputs.

◆ Where it's heading

The arc is consistently toward catching recoding mistakes at the call site rather than letting them pass silently. Early releases broadened how a match can be expressed — pattern matching, function application, factor and list returns. Recent work has shifted to guarantees about the result: correct factor level ordering relative to .default, and now an exhaustiveness check. Notably 0.4.0 reverses the 0.3.2 decision to accept arguments with or without dots, trading that flexibility for namespace safety against user-supplied case names.

◆ Prediction

The deprecation warnings introduced in 0.4.0 point to a follow-up release that removes the undotted arguments outright. Whether .exhaustive eventually becomes the default is unclear from these entries.

Alternatives to haze and incase

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either haze or incase.

See all haze alternatives → · See all incase alternatives →

Recent activity from haze and incase

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 18d agohazeVersion 0.3.0 -- Fixes and modernization
  2. 11mo agoincaseDotted arguments and an .exhaustive matching check
  3. 2y agoincaseDotted and undotted arguments both accepted
  4. 4y agohazev0.2.0 -- kdtrees
  5. 4y agohazev0.1.0: Initial release
  6. 5y agoincaseFix NULL return when no condition matches
  7. 5y agoincaseFactor and list return families arrive
  8. 5y agoincaseDrop unused stats import to clear a check NOTE
  9. 5y agoincasePattern and function-based matching families added

Frequently asked questions

What is the difference between haze and incase?

Both compete on the same themes — r-package — within Analytics. haze is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is haze better than incase?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. haze is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to haze?

Top haze alternatives in Analytics are ranked by recent ship velocity. Browse the "haze alternatives" section above for the current picks, or visit /alternatives/haze for the full list with editorial commentary on each.

What are the best alternatives to incase?

Top incase alternatives in Analytics are ranked by recent ship velocity. Browse the "incase alternatives" section above for the current picks, or visit /alternatives/incase for the full list with editorial commentary on each.