[clang-format] `AlignAfterOpenBracket: BlockIndent` produces inconsistent/bad formatting #55731

H-G-Hristov · 2022-05-27T11:52:58Z

My .clang-format file looks like:

---
BasedOnStyle: Google
Standard: c++20
IndentWidth: 4
ColumnLimit: 120
AccessModifierOffset: -4
AlignAfterOpenBracket: BlockIndent
AlignArrayOfStructures: Right
AllowShortEnumsOnASingleLine: false
AllowShortFunctionsOnASingleLine: Empty
AllowShortLambdasOnASingleLine: Empty
BinPackArguments: false
BinPackParameters: false
BraceWrapping:
  AfterClass: true
  AfterEnum: true
  AfterFunction: true
  AfterStruct: true
  AfterUnion: true
  BeforeLambdaBody: true
  SplitEmptyFunction: false
BreakBeforeBraces: Custom
BreakConstructorInitializers: BeforeComma
IncludeCategories:
  # Third party headers
  - Regex:           '^<(boost|bzip|fmt|grpc|gsl|gtest|gmock|isl|json|openssl|tl|toml\+\+|proto|zlib)/'
    Priority:        3
    SortPriority:    0
    CaseSensitive:   true
  # This library headers
  - Regex:           '^<(nblib)'
    Priority:        4
    SortPriority:    0
    CaseSensitive:   true
  # This library headers
  - Regex:           '^"(nblib)'
    Priority:        5
    SortPriority:    0
    CaseSensitive:   true
  # C system headers
  - Regex:           '^<.+\.h>$'
    Priority:        1
    SortPriority:    0
    CaseSensitive:   true
  # C++ standard library headers
  - Regex:           '^<.+'
    Priority:        2
    SortPriority:    0
    CaseSensitive:   true
  # Other headers
  - Regex:           '^".*'
    Priority:        6
    SortPriority:    0
    CaseSensitive:   true
IndentPPDirectives: AfterHash
PackConstructorInitializers: Never
# Different ways to arrange specifiers and qualifiers (e.g. const/volatile).
QualifierAlignment: Left
# Specifies the use of empty lines to separate definition blocks, including classes, structs, enums, and functions.
SeparateDefinitionBlocks: Always
# Add namespace comment after short namespaces
ShortNamespaceLines: 0
...

The result looks like:

#pragma once

#include <memory>
#include <optional>

#include <nblib/types/IForwardIterator.hpp>
#include <nblib/utilities/IFileSystem.hpp>
#include <nblib/utilities/Logging.hpp>

#include "nblib/data/hardware/IStorage.hpp"

namespace nblib::data {

#if defined(__APPLE__)
class ISystemProfiler;
#endif  // defined(__APPLE__)

}  // namespace nblib::data

namespace nblib::utilities {

#if defined(__linux__)
class IProcessSpawner;
#endif  // defined(__linux__)

}  // namespace nblib::utilities

namespace nblib::data {

using LogicalVolumeIteratorBase = nblib::types::IForwardIterator<IStorage::LogicalVolumeInfo>;

class Storage : public IStorage
{
public:
    Storage();

#if defined(__APPLE__)
    explicit Storage(std::unique_ptr<ISystemProfiler> systemProfiler);
#endif

#if defined(__linux__)
    explicit Storage(std::unique_ptr<::nblib::utilities::IProcessSpawner> processSpawner);
#endif

public:
    std::vector<LogicalVolumeInfo> GetLogicalVolumes() const noexcept override;

    std::vector<LogicalVolumeInfo> GetNonSystemLogicalVolumes() const noexcept override;

    std::vector<LogicalVolumeInfo> GetInternalNonRemovableLogicalVolumes() const noexcept override;

    std::vector<std::string> GetPhysicalDiskDriveNames() const noexcept override;

    std::vector<std::string> GetInternalNonRemovablePhysicalDiskDriveNames() const noexcept override;

    std::vector<OpticalDiscDriveInfo> GetOpticalDiscDrives() const noexcept override;

    std::vector<std::string> GetFloppyDiskDriveNames() const noexcept override;

    std::optional<PhysicalDiskDriveInfo> GetPhysicalDiskDriveInfo(const std::string& deviceName
    ) const noexcept override;

    std::optional<LogicalVolumeInfo> GetLogicalVolumeInfo(const std::string& deviceName) const noexcept override;

private:
    template <typename Iterator>
    std::optional<LogicalVolumeInfo> GetLogicalVolumeInfo(Iterator&& iterator, const std::string& deviceName)
        const noexcept;

private:
#if defined(__APPLE__)
    std::unique_ptr<ISystemProfiler> m_systemProfiler;
#endif  // __APPLE__

#if defined(__linux__)
    std::unique_ptr<::nblib::utilities::IProcessSpawner> m_processSpawner;
#endif  // __linux__
};

template <typename IteratorT>
std::optional<IStorage::LogicalVolumeInfo> Storage::GetLogicalVolumeInfo(
    IteratorT&& iterator, const std::string& deviceName
) const noexcept
{
    static_assert(std::is_base_of_v<LogicalVolumeIteratorBase, IteratorT>);

    try {
        LogicalVolumeInfo volumeInfo{};
        while (iterator.GetNext(volumeInfo)) {
            if (volumeInfo.deviceName == deviceName) {
                return volumeInfo;
            }
        }

        return {};
    } catch (const std::exception& e) {
        UCLOG_ERROR << "Unable to get logical volume info: " << e.what();

        return {};
    }
}

}  // namespace nblib::data

I would expect something like:

#pragma once

#include <memory>
#include <optional>

#include <nblib/types/IForwardIterator.hpp>
#include <nblib/utilities/IFileSystem.hpp>
#include <nblib/utilities/Logging.hpp>

#include "nblib/data/hardware/IStorage.hpp"

namespace nblib::data {

#if defined(__APPLE__)
class ISystemProfiler;
#endif  // defined(__APPLE__)

}  // namespace nblib::data

namespace nblib::utilities {

#if defined(__linux__)
class IProcessSpawner;
#endif  // defined(__linux__)

}  // namespace nblib::utilities

namespace nblib::data {

using LogicalVolumeIteratorBase = nblib::types::IForwardIterator<IStorage::LogicalVolumeInfo>;

class Storage : public IStorage
{
public:
    Storage();

#if defined(__APPLE__)
    explicit Storage(std::unique_ptr<ISystemProfiler> systemProfiler);
#endif

#if defined(__linux__)
    explicit Storage(std::unique_ptr<::nblib::utilities::IProcessSpawner> processSpawner);
#endif

public:
    std::vector<LogicalVolumeInfo> GetLogicalVolumes() const noexcept override;

    std::vector<LogicalVolumeInfo> GetNonSystemLogicalVolumes() const noexcept override;

    std::vector<LogicalVolumeInfo> GetInternalNonRemovableLogicalVolumes() const noexcept override;

    std::vector<std::string> GetPhysicalDiskDriveNames() const noexcept override;

    std::vector<std::string> GetInternalNonRemovablePhysicalDiskDriveNames() const noexcept override;

    std::vector<OpticalDiscDriveInfo> GetOpticalDiscDrives() const noexcept override;

    std::vector<std::string> GetFloppyDiskDriveNames() const noexcept override;

    std::optional<PhysicalDiskDriveInfo> GetPhysicalDiskDriveInfo(
       const std::string& deviceName
    ) const noexcept override;

    std::optional<LogicalVolumeInfo> GetLogicalVolumeInfo(const std::string& deviceName) const noexcept override;

private:
    template <typename Iterator>
    std::optional<LogicalVolumeInfo> GetLogicalVolumeInfo(
        Iterator&& iterator, const std::string& deviceName
    ) const noexcept;

private:
#if defined(__APPLE__)
    std::unique_ptr<ISystemProfiler> m_systemProfiler;
#endif  // __APPLE__

#if defined(__linux__)
    std::unique_ptr<::nblib::utilities::IProcessSpawner> m_processSpawner;
#endif  // __linux__
};

template <typename IteratorT>
std::optional<IStorage::LogicalVolumeInfo> Storage::GetLogicalVolumeInfo(
    IteratorT&& iterator, const std::string& deviceName
) const noexcept
{
    static_assert(std::is_base_of_v<LogicalVolumeIteratorBase, IteratorT>);

    try {
        LogicalVolumeInfo volumeInfo{};
        while (iterator.GetNext(volumeInfo)) {
            if (volumeInfo.deviceName == deviceName) {
                return volumeInfo;
            }
        }

        return {};
    } catch (const std::exception& e) {
        UCLOG_ERROR << "Unable to get logical volume info: " << e.what();

        return {};
    }
}

}  // namespace nblib::data

If a function declaration cannot fit on a single line it should preferably be broken after the opening and closing bracket always.

   ...

    // Fits on a single line:
    void myFunc2(int param) const noexcept;
    
    // Doesn't fit on a single line:
    void myFunc2(
        long long veryLongParametrName
    ) const noexcept;

   void myFunc3(
       int param1,
       int param2,
   ) const noexcept;
   
   // What about trailing return types?
   auto myFunc3(
       int param1,
       int param2,
   ) const noexcept -> std::vector<of_very_long_type>;

   auto myFunc3(
       int param1,
       int param2,
   ) const noexcept 
     -> std::vector<of_very_long_type>;

   ...

I love this new option but it needs work for braces {} and brackets (), etc.

References:

The text was updated successfully, but these errors were encountered:

H-G-Hristov · 2022-05-27T11:58:10Z

@csmulhern

llvmbot · 2022-05-27T13:27:49Z

@llvm/issue-subscribers-clang-format

stinos · 2022-06-22T19:26:18Z

Not sure if related, but there seems to be some strange interaction between using BlockIndent and the ContinuationIndentWidth value. Code:

int LotsOfArgs(int iddddddddddddddddddddddddddddddddddddddd, int aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa)
{
  const auto a = true || true || true || true || true || true || true || true || true || true || true || true || true || true || true || true || true || true;
  if( true || true || true || true || true || true || true || true || true || true || true || true || true || true || true || true || true || true )
  {}
}

with the settings shown above this gets turned into

int LotsOfArgs(
    int iddddddddddddddddddddddddddddddddddddddd,
    int aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
)
{
    const auto a = true || true || true || true || true || true || true || true || true || true || true || true ||
                   true || true || true || true || true || true;
    if (true || true || true || true || true || true || true || true || true || true || true || true || true || true ||
        true || true || true || true) {
    }
}

which is ok. Now I want 2 spaces for indent so change IndentWidth and ContinuationIndentWidth to 2, but then the if isn't broken anymore which isn't expected (more than 120 characters):

int LotsOfArgs(
  int iddddddddddddddddddddddddddddddddddddddd,
  int aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
)
{
  const auto a = true || true || true || true || true || true || true || true || true || true || true || true || true ||
                 true || true || true || true || true;
  if (true || true || true || true || true || true || true || true || true || true || true || true || true || true || true || true || true || true) {
  }
}

now change AlignAfterOpenBracket into Align and it breaks again:

int LotsOfArgs(int iddddddddddddddddddddddddddddddddddddddd,
               int aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa)
{
  const auto a = true || true || true || true || true || true || true || true || true || true || true || true || true ||
                 true || true || true || true || true;
  if (true || true || true || true || true || true || true || true || true || true || true || true || true || true ||
      true || true || true || true) {
  }
}

martinling · 2023-11-18T18:54:29Z

Since it seems this is now the chosen issue for tracking this bug, #54808 could be closed as another duplicate.

madmiraal · 2023-11-26T14:13:45Z

A simple version of the problem might help:
.clang-format:

AlignAfterOpenBracket: BlockIndent

Before:

// ----------------------------------------------------------- Column Width 80 >|<
bool ClassName::method(const bool &paramter1, const bool &parameter2) const {
  return true;
}

bool ClassName::longMethodName(const bool &paramter1, const bool &parameter2) const {
  return true;
}

bool ClassName::veryVeryLongMethodName(const bool &paramter1, const bool &parameter2) const {
  return true;
}

After:

// Good: Fits on one line
bool ClassName::method(const bool &paramter1, const bool &parameter2) const {
  return true;
}

// Bad: Unexpected!
bool ClassName::longMethodName(const bool &paramter1, const bool &parameter2)
    const {
  return true;
}

// Good: Expected
bool ClassName::veryVeryLongMethodName(
    const bool &paramter1, const bool &parameter2
) const {
  return true;
}

I've tried reducing the PenaltyBreakBeforeFirstCallParameter to 0 (I believe the default is 19) to encourage the break there, but that doesn't help.

.clang-format:

AlignAfterOpenBracket: BlockIndent
PenaltyBreakBeforeFirstCallParameter: 0

H-G-Hristov · 2023-12-07T16:04:35Z

A simple version of the problem might help: .clang-format:

AlignAfterOpenBracket: BlockIndent

Before:

// ----------------------------------------------------------- Column Width 80 >|<
bool ClassName::method(const bool &paramter1, const bool &parameter2) const {
  return true;
}

bool ClassName::longMethodName(const bool &paramter1, const bool &parameter2) const {
  return true;
}

bool ClassName::veryVeryLongMethodName(const bool &paramter1, const bool &parameter2) const {
  return true;
}

After:

// Good: Fits on one line
bool ClassName::method(const bool &paramter1, const bool &parameter2) const {
  return true;
}

// Bad: Unexpected!
bool ClassName::longMethodName(const bool &paramter1, const bool &parameter2)
    const {
  return true;
}

// Good: Expected
bool ClassName::veryVeryLongMethodName(
    const bool &paramter1, const bool &parameter2
) const {
  return true;
}

I've tried reducing the PenaltyBreakBeforeFirstCallParameter to 0 (I believe the default is 19) to encourage the break there, but that doesn't help.

.clang-format:

AlignAfterOpenBracket: BlockIndent
PenaltyBreakBeforeFirstCallParameter: 0

Your examples could also be expanded by placing a single parameter on a line:

void func(
   type1 param1,
   type2 param2,
   ...
)

madmiraal · 2023-12-08T11:39:08Z

Your examples could also be expanded by placing a single parameter on a line:
void func(
   type1 param1,
   type2 param2,
   ...
) 

This is a separate, but related issue i.e. AllowAllArgumentsOnNextLine: false is also not working with AlignAfterOpenBracket: BlockIndent even when setting BinPackArguments and BinPackParameters to false.

Expanded examples:
.clang-format:

AlignAfterOpenBracket: BlockIndent
AllowAllArgumentsOnNextLine: false
BinPackArguments: false
BinPackParameters: false
PenaltyBreakBeforeFirstCallParameter: 0
PenaltyReturnTypeOnItsOwnLine: 1000

class ClassName {
  // Expected: Fits on a single line
  bool method(const bool &parameter1, const bool &parameter2) const;

  // Expected: Fits on a single line
  bool longMethodName(const bool &parameter1, const bool &parameter2) const;

  // Unexpected: `const` on its own.
  bool veryVeryLongMethodName(const bool &parameter1, const bool &parameter2)
      const;

  // Unexpected: All parameters on the next line
  bool veryVeryVeryVeryLongMethodName(
      const bool &parameter1, const bool &parameter2
  ) const;

  // Expected: Each parameter on a separate line.
  bool method(
      const bool &parameter1,
      const bool &parameter2,
      const bool &parameter3,
      const bool &parameter4,
      const bool &parameter5
  ) const;
};

// ----------------------------------------------------------- Column Width 80
// >|<

// Expected: Fits on a single line
bool ClassName::method(const bool &parameter1, const bool &parameter2) const {
  return true;
}

// Unexpected: `const` on its own.
bool ClassName::longMethodName(const bool &parameter1, const bool &parameter2)
    const {
  return true;
}

// Unexpected: All parameters on the next line
bool ClassName::veryVeryLongMethodName(
    const bool &parameter1, const bool &parameter2
) const {
  return true;
}

// Unexpected: All parameters on the next line
bool ClassName::veryVeryVeryVeryLongMethodName(
    const bool &parameter1, const bool &parameter2
) const {
  return true;
}

// Expected: Each parameter on a separate line.
bool ClassName::method(
    const bool &parameter1,
    const bool &parameter2,
    const bool &parameter3,
    const bool &parameter4,
    const bool &parameter5
) const {
  return true;
}

For comparison it works as expected with AlignAfterOpenBracket: Align:

class ClassName {
  bool method(const bool &parameter1, const bool &parameter2) const;

  bool longMethodName(const bool &parameter1, const bool &parameter2) const;

  bool veryVeryLongMethodName(const bool &parameter1,
                              const bool &parameter2) const;

  bool veryVeryVeryVeryLongMethodName(const bool &parameter1,
                                      const bool &parameter2) const;

  bool method(const bool &parameter1,
              const bool &parameter2,
              const bool &parameter3,
              const bool &parameter4,
              const bool &parameter5) const;
};

// ----------------------------------------------------------- Column Width 80
// >|<

bool ClassName::method(const bool &parameter1, const bool &parameter2) const {
  return true;
}

bool ClassName::longMethodName(const bool &parameter1,
                               const bool &parameter2) const {
  return true;
}

bool ClassName::veryVeryLongMethodName(const bool &parameter1,
                                       const bool &parameter2) const {
  return true;
}

bool ClassName::veryVeryVeryVeryLongMethodName(const bool &parameter1,
                                               const bool &parameter2) const {
  return true;
}

bool ClassName::method(const bool &parameter1,
                       const bool &parameter2,
                       const bool &parameter3,
                       const bool &parameter4,
                       const bool &parameter5) const {
  return true;
}

EmrecanKaracayir · 2024-03-20T16:31:31Z

Any updates on this?

Here is how BlockIndent setting results with in my code:

void Workshop02::run()
{
  ANNOUNCE_WORKSHOP("Workshop 02: Uninitialized Variables & Undefined Behavior"
  );
  int x;
  std::cout << "Uninitialized variable x: " << x << '\n';
  std::cout << "Size of an int: " << sizeof(int) << '\n';
}

Expected result:

void Workshop02::run()
{
  ANNOUNCE_WORKSHOP(
    "Workshop 02: Uninitialized Variables & Undefined Behavior"
  );
  int x;
  std::cout << "Uninitialized variable x: " << x << '\n';
  std::cout << "Size of an int: " << sizeof(int) << '\n';
}

gedare · 2024-05-23T04:46:41Z

This is a separate, but related issue i.e. AllowAllArgumentsOnNextLine: false is also not working with AlignAfterOpenBracket: BlockIndent even when setting BinPackArguments and BinPackParameters to false.

Expanded examples: .clang-format:
AlignAfterOpenBracket: BlockIndent
AllowAllArgumentsOnNextLine: false
BinPackArguments: false
BinPackParameters: false
PenaltyBreakBeforeFirstCallParameter: 0
PenaltyReturnTypeOnItsOwnLine: 1000

Please retry with AllowAllParametersOfDeclarationOnNextLine: false

Fixes llvm#55731 Fixes llvm#73584 The reported formatting problems were related to ignoring deep nesting of "simple" functions (causing llvm#54808) and to allowing the trailing annotation to become separated from the closing parens, which allowed a break to occur between the closing parens and the trailing annotation. The fix for the nesting of "simple" functions is to detect them more carefully. "Simple" was defined in a comment as being a single non-expression argument. I tried to stay as close to the original intent of the implementation while fixing the various bad formatting reports. In the process of fixing these bugs, some latent bugs were discovered related to how JavaScript Template Strings are handled. Those are also fixed here.

madmiraal · 2024-06-04T06:21:32Z

Please retry with AllowAllParametersOfDeclarationOnNextLine: false

That works. 😄

So it's still just the const ending up on its own line when it's the only thing over the 80 column mark that is the problem:

AlignAfterOpenBracket: BlockIndent

// ----------------------------------------------------------- Column Width 80 >|<

// Good: Fits on one line
bool ClassName::method(const bool &paramter1, const bool &parameter2) const {
  return true;
}

// Bad: Unexpected const on its own!
bool ClassName::longMethodName(const bool &paramter1, const bool &parameter2)
    const {
  return true;
}

// Good: parameters on the next line,
// closing parenthesis and const on the following line.
bool ClassName::veryVeryLongMethodName(
    const bool &paramter1, const bool &parameter2
) const {
  return true;
}

Fixes llvm#55731 Fixes llvm#73584 The reported formatting problems were related to ignoring deep nesting of "simple" functions (causing llvm#54808) and to allowing the trailing annotation to become separated from the closing parens, which allowed a break to occur between the closing parens and the trailing annotation. The fix for the nesting of "simple" functions is to detect them more carefully. "Simple" was defined in a comment as being a single non-expression argument. I tried to stay as close to the original intent of the implementation while fixing the various bad formatting reports. In the process of fixing these bugs, some latent bugs were discovered related to how JavaScript Template Strings are handled. Those are also fixed here.

Summary: Fixes #55731 The reported formatting problems were related to ignoring deep nesting of "simple" functions (causing #54808) and to allowing the trailing annotation to become separated from the closing parens, which allowed a break to occur between the closing parens and the trailing annotation. The fix for the nesting of "simple" functions is to detect them more carefully. "Simple" was defined in a comment as being a single non-expression argument. I tried to stay as close to the original intent of the implementation while fixing the various bad formatting reports. In the process of fixing these bugs, some latent bugs were discovered related to how JavaScript Template Strings are handled. Those are also fixed here. --------- Co-authored-by: Owen Pan <[email protected]> Test Plan: Reviewers: Subscribers: Tasks: Tags: Differential Revision: https://phabricator.intern.facebook.com/D60250557

github-actions bot added the new issue label May 27, 2022

EugeneZelenko added clang-format and removed new issue labels May 27, 2022

Zingam mentioned this issue Nov 26, 2022

clang-format: breaking parameters and arguments #53190

Open

This was referenced Nov 18, 2023

[clang-format] BlockIndent defect #63383

Closed

[clang-format] AlignAfterOpenBracket: BlockIndent: weird close-bracket when ')' or qualifiers exceeds ColumnLimit #55473

Closed

Zingam mentioned this issue Nov 25, 2023

[clang-format] Misformatting with AlignAfterOpenBracket: BlockIndent #54808

Closed

gedare mentioned this issue Nov 30, 2023

clang-format: Behavior changes between 16.0 and 17.0 #73584

Closed

gedare mentioned this issue May 23, 2024

[clang-format] Improve BlockIndent at ColumnLimit #93140

Merged

owenca closed this as completed in #93140 Jul 25, 2024

owenca closed this as completed in ccae7b4 Jul 25, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[clang-format] `AlignAfterOpenBracket: BlockIndent` produces inconsistent/bad formatting #55731

[clang-format] `AlignAfterOpenBracket: BlockIndent` produces inconsistent/bad formatting #55731

H-G-Hristov commented May 27, 2022 •

edited

Loading

H-G-Hristov commented May 27, 2022

llvmbot commented May 27, 2022

stinos commented Jun 22, 2022 •

edited

Loading

martinling commented Nov 18, 2023

madmiraal commented Nov 26, 2023

H-G-Hristov commented Dec 7, 2023

madmiraal commented Dec 8, 2023

EmrecanKaracayir commented Mar 20, 2024 •

edited

Loading

gedare commented May 23, 2024

madmiraal commented Jun 4, 2024

[clang-format] AlignAfterOpenBracket: BlockIndent produces inconsistent/bad formatting #55731

[clang-format] AlignAfterOpenBracket: BlockIndent produces inconsistent/bad formatting #55731

Comments

H-G-Hristov commented May 27, 2022 • edited Loading

H-G-Hristov commented May 27, 2022

llvmbot commented May 27, 2022

stinos commented Jun 22, 2022 • edited Loading

martinling commented Nov 18, 2023

madmiraal commented Nov 26, 2023

H-G-Hristov commented Dec 7, 2023

madmiraal commented Dec 8, 2023

EmrecanKaracayir commented Mar 20, 2024 • edited Loading

gedare commented May 23, 2024

madmiraal commented Jun 4, 2024

[clang-format] `AlignAfterOpenBracket: BlockIndent` produces inconsistent/bad formatting #55731

[clang-format] `AlignAfterOpenBracket: BlockIndent` produces inconsistent/bad formatting #55731

H-G-Hristov commented May 27, 2022 •

edited

Loading

stinos commented Jun 22, 2022 •

edited

Loading

EmrecanKaracayir commented Mar 20, 2024 •

edited

Loading