feat: add ml/base/sgd-classification/loss-functions

[nakul-krishnakumar]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown_pkg_readmes status: passed
• task: lint_markdown_docs status: na
• task: lint_markdown status: na
• task: lint_package_json status: passed
• task: lint_repl_help status: passed
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: passed
• task: lint_javascript_tests status: passed
• task: lint_javascript_benchmarks status: passed
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: passed
• task: lint_typescript_tests status: passed
• task: lint_license_headers status: passed ---

Resolves a part of #12875.

Description

What is the purpose of this pull request?

This pull request:

• Add ml/base/sgd-classification/loss-functions.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• [RFC]: Add batch machine learning algorithms in Javascript and C (tracking issue) #12875

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
ml/base/sgd-classification/loss-functions	$\\color{green}163/163$ $\\color{green}+0.00\\%$	$\\color{green}5/5$ $\\color{green}+0.00\\%$	$\\color{green}2/2$ $\\color{green}+0.00\\%$	$\\color{green}163/163$ $\\color{green}+0.00\\%$

The above coverage report was generated for the changes in this PR.

[kgryte]

Sorry to be pedantic, but would you mind ordering in alphabetical order? This helps with visual scanning. Namely, it is easier for a reader to scan a sorted list than it is an unsorted list.

[kgryte]

This will impact all the docs and tests in this package.

[nakul-krishnakumar]

Sure, will do 👍

[kgryte]

Sanity check. For these types of things, do we have any precedent for using camelcase rather than kebabcase?

[kgryte]

I.e., epsilonInsensitive vs epsilon-insensitive

[nakul-krishnakumar]

https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/ml/incr/binary-classification#:~:text=loss,Default%3A%20%27log%27%2E

I would be happy to switch to kebabcase

[kgryte]

Here is another example where we use kebabcase: https://github.com/stdlib-js/stdlib/tree/refactor/plot/lib/node_modules/%40stdlib/plot/vega/mark/interpolation-methods

In short, I think ml/incr/binary-classification is the odd one out here and we should make a breaking change in that package to use kebabcase for the option values.

You in agreement?

[kgryte]

Feel free to either open a PR making the change on that package, or, at minimum, opening an issue so we don't forget to make the change.

[nakul-krishnakumar]

Yes I completely agree with you here.
So as mentioned above I will be refactoring the enum in this package from camelcase to kebabcase, after which I will raise a PR to do the same for ml/incr/binary-classification. 🚀

[nakul-krishnakumar]

I noticed that ml/incr/sgd-regression also follows camelcase for loss functions. I will open an issue mentioning both the packages.

[kgryte]

Left initial comments.