Corrected multiple comments to use correct Swift syntax

[elaewin]

Multiple comments in multiple files were commented with a triple slash (///) which is the correct syntax for C#, but not for Swift. This was causing multiple warnings in Xcode.

A slash was removed where necessary to give the comments the correct double slash syntax for Swift comments.

[codecov-io]

Codecov Report

Merging #2399 into master will not change coverage.
The diff coverage is 21.27%.

@@           Coverage Diff           @@
##           master    #2399   +/-   ##
=======================================
  Coverage   19.66%   19.66%           
=======================================
  Files         112      112           
  Lines       13712    13712           
=======================================
  Hits         2696     2696           
  Misses      11016    11016

Impacted Files	Coverage Δ
Source/Charts/Renderers/BarChartRenderer.swift	41.78% <ø> (ø)	⬆️
Source/Charts/Renderers/PieChartRenderer.swift	0% <ø> (ø)	⬆️
Source/Charts/Components/ChartLimitLine.swift	0% <ø> (ø)	⬆️
Source/Charts/Highlight/Highlight.swift	0% <ø> (ø)	⬆️
Source/Charts/Utils/ChartUtils.swift	35.21% <ø> (ø)	⬆️
Source/Charts/Renderers/RadarChartRenderer.swift	0% <ø> (ø)	⬆️
...rts/Renderers/LineScatterCandleRadarRenderer.swift	9.09% <ø> (ø)	⬆️
Source/Charts/Highlight/Range.swift	0% <ø> (ø)	⬆️
...ta/Implementations/Standard/LineChartDataSet.swift	22.38% <ø> (ø)	⬆️
...Data/Implementations/Standard/RadarChartData.swift	0% <ø> (ø)	⬆️
... and 71 more

---

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 5288c25...ce7bf0e. Read the comment docs.

[thierryH91200]

are you sure ?????

on a function with Xcode

and the result

on playground
type

/// This is an awesome documentation line for a really useful variable.
var someVar = "This is a variable"

Option/Alt-Clicking to the name of a property, method, class,

[elaewin]

The triple slashes for document markup are what is causing the errors in issues #135, and #2316.