Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Algorithm updates #3638

Merged
merged 4 commits into from
Dec 15, 2020
Merged

Algorithm updates #3638

merged 4 commits into from
Dec 15, 2020

Conversation

jjatie
Copy link
Collaborator

@jjatie jjatie commented Sep 17, 2018

Goals ⚽

Inspired by WWDC'18 Embracing Algorithms
Charts relies heavily on custom algorithm implementations. Many of these are common algorithms and should instead rely on the built in implementations. In this PR I have updated the obvious candidates.

I have intentionally omitted the longer algorithms as some A) are unique algorithms and B) can become much simpler with some additional changes in the framework (i.e. Collection conformances introduced in 4.0.0).

@liuxuan30
Copy link
Member

liuxuan30 commented Sep 19, 2018

May take longer to dig. I remember when Swift 1.2/2.2 was there, the performance is bad. So @danielgindi choose to write our own?

Cartfile.resolved Outdated Show resolved Hide resolved
@codecov-io
Copy link

codecov-io commented Mar 9, 2019

Codecov Report

Merging #3638 into master will decrease coverage by 0.02%.
The diff coverage is 10.93%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #3638      +/-   ##
==========================================
- Coverage   32.64%   32.61%   -0.03%     
==========================================
  Files         114      114              
  Lines       10625    10625              
==========================================
- Hits         3468     3465       -3     
- Misses       7157     7160       +3
Impacted Files Coverage Δ
Source/Charts/Charts/PieRadarChartViewBase.swift 4.59% <ø> (ø) ⬆️
Source/Charts/Components/ChartLimitLine.swift 0% <ø> (ø) ⬆️
...ts/Renderers/YAxisRendererHorizontalBarChart.swift 0% <0%> (ø) ⬆️
...ts/Renderers/XAxisRendererHorizontalBarChart.swift 0% <0%> (ø) ⬆️
Source/Charts/Renderers/YAxisRenderer.swift 54.86% <0%> (ø) ⬆️
Source/Charts/Renderers/XAxisRenderer.swift 61.58% <12.72%> (-0.92%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 35a47a4...b14b75d. Read the comment docs.

@liuxuan30
Copy link
Member

@jjatie 3.3 is just released :) I think we can focus on 4.0 now. So much in plate 😂

@jjatie jjatie merged commit 0aa2b76 into master Dec 15, 2020
@jjatie jjatie deleted the algorithm-updates branch December 15, 2020 21:32
abhiramvadlapatla pushed a commit to abhiramvadlapatla/Charts that referenced this pull request Dec 21, 2021
* algorithm updates

* Minor code org updates

* Relocated util file

* Removed duplicated file

akjflkajfljk
zebraciam added a commit to zebraciam/Charts that referenced this pull request Jul 6, 2022
* master:
  update changelog.
  Fixed incorrect guard return statement when rendering limit lines (ChartsOrg#4563)
  Fix bounds checks on binary search (ChartsOrg#4577)
  Added SPM build action (ChartsOrg#4576)
  Replace FBSnapshotTestCase with pointfree/swift-snapshot-testing (ChartsOrg#4574)
  Import swift algorithms (ChartsOrg#4497)
  ChartViewBase cleanup (ChartsOrg#4537)
  SPM GitHub Action (ChartsOrg#4553)
  Algorithm updates (ChartsOrg#3638)
  Added SPM Install section
  Update README.md
  Fix missing drawIconsEnabled parameter initialization in the copying constructor of the ChartBaseDataSet (ChartsOrg#4424)
  Resolve conflict for 4.0 branch and master (ChartsOrg#4456)
  Alternative for SPM dynamic linking (ChartsOrg#4478)
  3.6.0 changelog

# Conflicts:
#	Source/Charts/Renderers/LineChartRenderer.swift
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.

3 participants