Files
mp-units/HEAD/feed_json_created.json
T

1 line
17 KiB
JSON
Raw Normal View History

{"version": "https://jsonfeed.org/version/1", "title": "mp-units", "home_page_url": "https://mpusz.github.io/mp-units/HEAD/", "feed_url": "https://mpusz.github.io/mp-units/HEAD/feed_json_created.json", "description": "The quantities and units library for C++", "icon": null, "authors": [{"name": "mp-units Team"}], "language": "en", "items": [{"id": "https://mpusz.github.io/mp-units/HEAD/blog/2025/06/16/introducing-absolute-quantities/", "url": "https://mpusz.github.io/mp-units/HEAD/blog/2025/06/16/introducing-absolute-quantities/", "title": "Introducing absolute quantities", "content_html": "<h1>Introducing absolute quantities</h1>\n<p>This post introduces a new abstraction called an absolute quantity. It complements affine\nspace abstractions (point and delta) and will most probably be a new default in the library\nwhen we release V3.</p>", "image": "https://mpusz.github.io/mp-units/HEADassets/images/social/blog/posts/introducing-absolute-quantities.png", "date_published": "2025-06-16T00:00:00+00:00", "authors": [{"name": "Mateusz Pusz"}], "tags": ["Metrology"]}, {"id": "https://mpusz.github.io/mp-units/HEAD/blog/2025/01/15/bringing-quantity-safety-to-the-next-level/", "url": "https://mpusz.github.io/mp-units/HEAD/blog/2025/01/15/bringing-quantity-safety-to-the-next-level/", "title": "Bringing Quantity-Safety To The Next Level", "content_html": "<h1>Bringing Quantity-Safety To The Next Level</h1>\n<p>All quantities and units libraries need to be unit-safe. Most of the libraries on the market do\nthis correctly. Some of them are also dimension-safe, which adds another level of protection for\ntheir users.</p>\n<p><strong>mp-units</strong> is probably the only library on the market that additionally is quantity-safe. This\ngives a new quality and possibilities. I've described the major idea behind it, implementation\ndetails, and benefits to the users in the <a href=\"isq-part-5-benefits.md\">series of posts about the International System of Quantities</a>.</p>\n<p>However, this is only the beginning. We've always planned more and worked on the extensions in our\nfree time. In this post, I will describe:</p>\n<ul>\n<li>What a quantity character is?</li>\n<li>The importance of using proper representation types for the quantities.</li>\n<li>The power of providing character-specific operations for the quantities.</li>\n<li>Discuss implementation challenges and possible solutions.</li>\n</ul>", "image": "https://mpusz.github.io/mp-units/HEADassets/images/social/blog/posts/bringing-quantity-safety-to-the-next-level.png", "date_published": "2025-01-15T00:00:00+00:00", "authors": [{"name": "Mateusz Pusz"}], "tags": ["Metrology"]}, {"id": "https://mpusz.github.io/mp-units/HEAD/blog/2024/11/25/report-from-the-wroc%C5%82aw-2024-iso-c-committee-meeting/", "url": "https://mpusz.github.io/mp-units/HEAD/blog/2024/11/25/report-from-the-wroc%C5%82aw-2024-iso-c-committee-meeting/", "title": "Report from the Wroc\u0142aw 2024 ISO C++ Committee meeting", "content_html": "<h1>Report from the Wroc\u0142aw 2024 ISO C++ Committee meeting</h1>\n<p>The Wroc\u0142aw 2024 meeting was another efficient step in the standardization of this library.\nWe've spent the entire day on the joint LEWGI and SG6 discussion and got lots of feedback.\nWe've also introduced <code>std::fixed_string</code> to LEWG for C++26.</p>", "image": "https://mpusz.github.io/mp-units/HEADassets/images/social/blog/posts/wroc\u0142aw-2024-report.png", "date_published": "2024-11-25T00:00:00+00:00", "authors": [{"name": "Mateusz Pusz"}], "tags": ["WG21 Updates"]}, {"id": "https://mpusz.github.io/mp-units/HEAD/blog/2024/11/11/international-system-of-quantities-isq-part-6---challenges/", "url": "https://mpusz.github.io/mp-units/HEAD/blog/2024/11/11/international-system-of-quantities-isq-part-6---challenges/", "title": "International System of Quantities (ISQ): Part 6 - Challenges", "content_html": "<h1>International System of Quantities (ISQ): Part 6 - Challenges</h1>\n<p>This article might be the last one from our series. This time, we will discuss the challenges and\nissues with m