fix site

Author: Quafadas

jsSite/src/BenchmarkPlots.scala

@@ -4,9 +4,7 @@ import scala.NamedTuple.AnyNamedTuple
 import scala.annotation.meta.field
 import upickle.default.*
 import NamedTupleReadWriter.given
-import scala.annotation.experimental
 
-@experimental()
 object BenchmarkPlots:
   def addScalarBenchmark: String =
     val thePlot = BenchmarkPlotElements.schema ++

jsSite/src/PlotElements.scala

@@ -1,6 +1,5 @@
 package vecxt.plot
 
-// import scala.NamedTuple.*
 import scala.annotation.meta.field
 import upickle.default.*
 import NamedTupleReadWriter.given

jsSite/src/facade.scala

@@ -29,7 +29,6 @@ import org.scalajs.dom.Element
 import org.scalajs.dom.XMLHttpRequest
 import scala.annotation.experimental
 
-@experimental()
 object showJsDocs:
   def apply(path: String, node: Element, width: Int = 50) =
     val child = dom.document.createElement("div")

site/docs/_blog/_posts/2025-06-04-Performance Perils.md

@@ -46,7 +46,9 @@ it's simply too natural to write
 For this, you pay a cca 10x performance cost, and it's actually pretty hard to see it's happening, unless you break out the profiler and zoom right in. I can't see a great ways around this. Operations at high risk of clashing, are therefore named with a SIMD suffix. The sensibly named counterparts remain, but it's on you to call them correctly.
 
 ```scala
-val a = Array[Double](1, 2, 3)
+import vecxt.all.*
+
+val a = Array[Double](1, 2, 3, 6, 10, -100)
 
 a.sumSIMD // SIMD optimized sum
 a.productSIMD // SIMD optimized product