Skip to content

Comments

Feature/mesh geometry-connectivity split#1018

Draft
adampep wants to merge 84 commits intodevelopfrom
feature/mesh_geom_comm
Draft

Feature/mesh geometry-connectivity split#1018
adampep wants to merge 84 commits intodevelopfrom
feature/mesh_geom_comm

Conversation

@adampep
Copy link
Collaborator

@adampep adampep commented Oct 30, 2023

Starting a discussion regarding code structure

@adampep adampep added enhancement New feature or request don't merge Don't merge yet! refactor labels Oct 30, 2023
@adampep adampep self-assigned this Nov 2, 2023
@timofeymukha
Copy link
Collaborator

Hi! I think these comments will be it for me. As I wrote previously on Zulip, I would generally like the enforcement of
"Prepend the implementations of type-bound procedures (TBPs) with the name of the type, sans the _t."
to be strict.

I did find it hard to keep track of all the types when doing the review, and I think the extra helper types that just wrap an allocatable to increase that issue quite considerably. I would therefore be in favour of enforcing some convention for those, as currently defined in at topic on Zulip. But I don't think this should prevent the merge atm, we can do that later.

I think we will also need some kind of "developer guide" discussing some of the questions that pop up. Maybe extended module level docstrings similar to that I added for the alignment. I honestly think things might become clear as the _topology and _mesh objects actually become used. So we can do that in a alter PR as well.

@ExtremeFLOW ExtremeFLOW deleted a comment from timofeymukha Feb 21, 2024
@adampep adampep added the don't merge Don't merge yet! label Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

don't merge Don't merge yet! enhancement New feature or request refactor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants